Re: seg fault on startup

[Andrew Haley <aph at redhat dot com>]

Top-posting fixed.

Ben Tatham writes:
 > 
 > Andrew Haley wrote:
 > > Ben Tatham writes:
 > >  > wow.  fast response.  does "debuginfo" refer to something i'm not 
 > >  > familiar with, or is that just generic debug info?    what sort of other 
 > >  > info do you need...i tried to give as much of the enviroment that I 
 > >  > thought necessary.
 > >  > 
 > >  > Yes, I have tried it with libgcj stripped, and well as unstripped.  I 
 > >  > have tried things with both libc 2.3.3 and libc 2.3.6.  (We prefer to 
 > >  > stay at libc 2.3.3 so we don't have to change others of our linux bins, 
 > >  > but it doesn't work either anyway...)
 > >
 > > Referring to the fact that in your gdb backtrace there are neither
 > > line numbers nor function args.  We need those.  This lack is probably
 > > due to debuginfo being stripped.
 >
 > Ah...that raises another question.  We are using crosstool (i686 with ed 
 > hat enterprise linux 3) to compile our app.  However, when I try to run 
 > Foo unstripped inside gdb on the target (ppc860, 66MHz, 128MB ram), gdb 
 > itself seg faults. 

OK, so you have a very resource limited target.  Fair enough.

 > As it does when I try to analyze the core afterward.  I do have the
 > xtool version of gdb on our build server, but I am having trouble
 > getting it to load the target libs instead of the native ones.  Any
 > advice on how to do that when analyzing a core file?

I might have, if you told me what the trouble was!  I'm not (quite) a
miracle worker.  :-)

Andrew.