http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57688
--- Comment #4 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Mikael Pettersson from comment #1) > Run it in gdb, wait for the fault, and disassemble the code around the > faulting PC. That valgrind report doesn't really say anything useful. 0x00000000004045d4 <+948>: lea -0x5(%r9),%edx 0x00000000004045d8 <+952>: lea 0x140(%r10),%rsi 0x00000000004045df <+959>: mov %rax,%rcx => 0x00000000004045e2 <+962>: bextr $0x1e02,%rdx,%rdx 0x00000000004045eb <+971>: xor %r8d,%r8d 0x00000000004045ee <+974>: shl $0x6,%rdx 0x00000000004045f2 <+978>: lea 0x180(%r10,%rdx,1),%rdi
