|
From: Steve B. <Ste...@an...> - 2005-07-09 00:40:27
|
Hi Julian, >I'm looking at reimplementing INT in Valgrind 3. V3 has a completely >new JIT compared to Valgrind 2, and INT died in the transition >(obviously int $0x80 works, but nothing else). > >So I'm trying to understand the requirements people have. > >Chris, you appear to require that execution of int3 causes SIGTRAP >to be delivered. > >Steve, you appear to require that execution of int $0x40 .. $0x43 >cause SIGTRAP to be delivered? > > My requirements are really just that I see the same behavior under valgrind as when running natively, given that we do use int $0x40...$0x43. As I understand it, we just get a signal which looks like a SIGSEGV and we figure things out from there by looking at the gregs. I've attached the correspondance I had with Jeremy which lead to his fix. Cheers, --Steve |