On Thursday, April 26, 2012, John Reiser wrote:
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.]
It
Hello,
Is there any way how to suppress the messages from the library instead
of installing a debug version? Most distributions do not have debug
versions of all the libraries, and I want to suppress the allocations
from that library anyway.
Best regards
Marian
On Thu, 2012-04-26 at 09:29 -0400, Matt Broadstone wrote:
As for doing a db-attach, that seems to have failed as well - I never
make it to a gdb session. Here is the full output of a db-attach
valgrind run on TextEdit.app:
==76980== Attach to debugger ? --- [Return/N/n/Y/y/C/c]
On Thu, Apr 26, 2012 at 2:06 PM, Philippe Waroquiers
philippe.waroqui...@skynet.be wrote:
On Thu, 2012-04-26 at 09:29 -0400, Matt Broadstone wrote:
As for doing a db-attach, that seems to have failed as well - I never
make it to a gdb session. Here is the full output of a db-attach
valgrind
On Thu, 2012-04-26 at 14:17 -0400, Matt Broadstone wrote:
and then:
(gdb) target remote | /usr/local/bin/vgdb
| /usr/local/bin/vgdb: Undefined error: 0
You must have a version of gdb recent enough (I believe = 6.5)
otherwise GDB does not understand the | target.
Two alternatives:
*
On Thu, Apr 26, 2012 at 3:27 PM, Philippe Waroquiers
philippe.waroqui...@skynet.be wrote:
On Thu, 2012-04-26 at 14:17 -0400, Matt Broadstone wrote:
and then:
(gdb) target remote | /usr/local/bin/vgdb
| /usr/local/bin/vgdb: Undefined error: 0
You must have a version of gdb recent enough
Okay, I was able to get that working. Here is the result of
disassembling that instruction:
0x03a36b8c __abort+225: ud2a
Yeah, so as expected it's died on ud2a, as the
vex amd64-IR: unhandled instruction bytes: 0xF 0xB
line implies -- 0F 0B is ud2a.
The real question is, why
