https://bugs.kde.org/show_bug.cgi?id=374596
--- Comment #6 from bugzi...@dcopp.net --- (In reply to Tom Hughes from comment #4) > Ah sorry I misunderstood your original report... > > You're saying that valgrind aborts on the instruction even though you don't > try and execute it. My guess is that it's happening because that will be > reported at translation time and valgrind translates instructions in blocks > so it may translate an instruction that never gets executed. This is contrary to how the processor works. A program can have potentially any number of regions in the code segment that do not contain valid opcodes and are never executed (despite routinely making their way into the processor's prefetch/decode queue.) An illegal instruction exception only arises from an actual attempted execution. But let's suppose your guess about valgrind's behavior is correct. How would one rewrite this test program to ensure that the inclusion (but not execution) of the RDTSCP opcode would not provoke this problem under valgrind? -- You are receiving this mail because: You are watching all bug changes.
