> Can you point me towards how to get you the information you require?
It's a *BUG* in valgrind that valgrind does not print the bytes [or words, etc.]
of the instruction stream that valgrind does not understand.
[This is immediately obvious to *EVERY* user, but so far the developers
have been oblivious.]
So, users must spoon-feed the developers.. Invoke valgrind using:
$ valgrind --db-attach=yes <other valgrind options> /path/to/my/app <args to
the app>
Then when valgrind encounters the error and asks what to do, answer 'Y'
for "yes, please attach the debugger now". Soon you should get a gdb prompt:
(gdb)
At this gdb prompt, enter the commands to examine memory at the suspect address.
For example,
==66368== valgrind: Unrecognised instruction at address 0x3a36b8c.
Attach to debugger now? [Y/y/N/n/...] Y ### not an exact quotation
(gdb) x/4xw 0x3a36b8c
(gdb) x/4i 0x3a36b8c
(gdb) x/12i 0x3a36b8c-0x18
which says "examine memory, and print 4 words in hex beginning at the
address of the troublesome opcode. Then "examine memory, and print
4 instructions beginning at the address of the troublesome instruction".
Then "examine memory, and print 12 instructions beginning 0x18 bytes
before the troublesome instruction". Then copy+paste all that
into the valgrind bug report.
--
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
