Hey all,
while trying to debug a LLVM-based application, I get the following output.
vex amd64->IR: unhandled instruction bytes: 0xC5 0xF9 0x57 0xC0 0xC6
0x83 0xDC 0xD
==17842== valgrind: Unrecognised instruction at address 0x5630b64.
==17842== at 0x5630B64:
llvm::X86TargetLowering::X86TargetL
()= 30593
the file descriptors 1016, 1017 and 1018 belong to valgrind, and it looks like
valgrind is very talkative to my app (or the other way around) with just a
singe letter byte incrementing on each write()/read() to/from its pipe.
hey,
I just can't help myself anymore in getting those f***g glibc errors off
the screen.
I also can't believe, that I am expected to generate a big list of
suppression files just to make valgrind not complain about glibc - even
when running /bin/echo.
IIRC someone once told, these are because gl
