threads/2292: GDB process stops when debugging threaded program
Oleg V. Zhylin
ovz@yahoo.com
Wed Nov 14 22:27:00 GMT 2007
Sorry for not looking this up myself, I definitely should have. It
seems like a lot of people use "pure" gdb (w/o DDD or other "shells")
for pthread projects debugging, but for some reason I experience
behavior described threads/2292 on every Linux box I have access to.
Looks like I'm missing something obvious, but I would be very grateful
if someone points out what is it exactly.
--- Daniel Jacobowitz <drow@false.org> wrote:
> On Wed, Nov 14, 2007 at 03:33:20AM -0800, Oleg V. Zhylin wrote:
> > Hi,
> >
> > As this issue came up again, I've checked with DDD folks, since
> DDD
> > steps through threads successfully. DDD does use gdb as debugging
> > engine, so clearly it does some configuraiton. We didn't figure out
> > what exactly DDD does, but the effect of it is that gdb locates
> > /lib/libthread_db.so.1. Thus it looks like my problem can be
> > re-formulated
> >
> > How to make gdb locate libpthread_db library?
>
> Take a look at the messages from the first message you posted about
> the bug. GDB already was finding libthread_db.so.1. If it can't, it
> will let you know loudly.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>
WBR Oleg V. Zhylin ovz@yahoo.com
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
More information about the Gdb
mailing list