https://bugs.kde.org/show_bug.cgi?id=369854
Ivo Raisr <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Ivo Raisr <[email protected]> --- I see you are stuck among all different parties, everyone saying "our part behaves ok; it's not our fault". At this point I'd suggest you do as folks on Intel forum suggested, in combination with gdb+vgdb [1]. Use '--vgdb-error=1' or an appropriate number which will stop the execution right upon reaching the reported problem. Disassemble the offending part of __intel_new_memcpy(), observe values of relevant registers and report back here. [1] http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver -- You are receiving this mail because: You are watching all bug changes.
