Re: Insight cross-debugging fails... ?

[Keith Seitz <keiths at redhat dot com>]

Paul Smith wrote:
> However, if I try to debug using powerpc-linux-gnu-insight instead of
> gdb, it fails with a SIGILL.  I start insight and I get a warning "Make
> breakpoint depending on future shared library load?"  I don't understand
> this but I say "Ok" (I've tried saying "no" and it fails the same way).

"Make breakpoint pending on future shared library load?" means that the 
symbol for which a breakpoint is requested is unknown. It thinks that 
you want to set a break on some function that is in a shared library 
that is not yet loaded.

Do you have exec and symbol files specified? Can you open a console 
window and "list" the function? What run options are specified?

> I click the run button and I get an error dialog: "Program received
> SIGILL: Illegal instruction".  If I click OK, the target program just
> fails.

Hmm. That is a little odd.

> This has to be something odd that the insight code is doing, because
> both vanilla GDB 6.5 and the command line gdb generated by the Insight
> build work fine.

Can you do your command line debugging from insight's console window? 
That might help to start eliminating possible points of trouble.

> Anyone have any thoughts?  Should this work? 

I would think this should work, yes.

Keith