This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Need help with a backtrace

Fernando Nasser wrote:
> Matt Schalit wrote:

Thanks again for the reply.  My followup was stuck in Pacbell's
queue for a few days, during which time I figured out how
to make the info files and read them.

Your post definitely helped me and confirmed what I read.

Btw, that was one of the best info files I've ever seen.
It was very intuitive and logical in it's layout.
Thanks to everyone who worked on that, for sure!

Now I finally understand about breakpoints, and will
just have to man handle it a bit until I get good. 

They're a bit swamped over in the gnome bugs department,
and I haven't heard anything back on this.  Part of the 
problem is that there are so many lists that things slip by.  
I'll have to post to them again with a better subject line.


I'm going to stick a final question in down here, in case you've
read this far :)  

In general, when a backtrace gives a really meager output 
like the following:

> > (gdb) file /usr/local/cgi-bin/convert
> > (gdb) run
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x80016d76 in ?? () from /usr/lib/
> > (gdb) bt
> > #0  0x80016d76 in ?? () from /usr/lib/
> > #1  0x80016c5c in ?? () from /usr/lib/
> > #2  0x8001826d in ?? () from /usr/lib/
> > #3  0x8001932d in ?? () from /usr/lib/
> > #4  0x80014b20 in ?? () from /usr/lib/

and that's all the lines it output, am I supposed to
put breakpoints into my convert program to see when
it makes a call to a libc function?  I can't understand 
why there's so little info nor why it left out the function 

Thanks again for your help!

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]