Re: [Valgrind-users] unhandled instruction bytes..

[Jeremy F. <je...@go...>]

On Fri, 2003-07-25 at 06:41, Nicholas Nethercote wrote:
> On Fri, 25 Jul 2003, Rob Kramer wrote:
> 
> > It dies as soon as I open a graphics screen - I'd suspect the 'unhandled
> > instructions', but I don't know enough about valgrind yet to have a valid
> > opinion :)
> 
> I definitely suspect the "unhandled instruction", since it comes before
> the "illegal instruction".  It's strange, normally when Valgrind sees an
> instruction it can't handle, it aborts, I wonder why it continues
> executing with your program... something weird.

I made a change a while ago so that unknown/illegal instructions get
turned into illegal instructions in the generated code rather than
simply crashing Valgrind.  I did this to handle code which tries to see
if the CPU has a certain instruction by just running it and catching the
SIGILL.

	J