Re: [Valgrind-users] SIGILL on PPC Book E Architecture.

[Julian S. <js...@ac...>]

> Thanks for the suggestion.  Unfortunately, the address where the illegal
> instruction is occurring is nowhere near any of the library addresses,
> and it looks like it's actually on the heap somewhere, according to
> /proc/$pid/maps.  Is the core file Valgrind generates of any use in this
> situation?

I just remembered, when Valgrind's powerpc instruction decoder hits
an instruction it doesn't like, it prints some stuff about the
primary and secondary opcode and what the instruction actually is.
Do you have that info?

But in any case .. if you think that V is executing in the middle of
the heap, maybe your program did a bogus jump?  If so, that tends to
be symptomatic of type confusion in C++ code -- often in very 
obscure ways to do with inheritance.

J