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 always prints the bytes of the instruction it can't parse. Without that we'd never be able to make sense of any "unhandled insn" style bug reports. It seems like you removed them from the initial posting, though. Do you have a line of the form vex amd64->IR: unhandled instruction bytes: 0xC5 0xF8 0x77 0xC3 0xF6 Anyway, I suspect that will merely tell us that abort crapped out on 0x0F 0x0D, which is the official undefined instruction "ud2", so that's not useful. We need to know why the program jumped to abort() in the first place. The svn trunk does work on OSX 10.7.3 -- I was working with it at the weekend. Really what is needed is a way to reproduce this failure. J ------------------------------------------------------------------------------ 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
