From: "Oleg V. Zhylin" <ovz@yahoo.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: threads/2292: GDB process stops when debugging threaded program
Date: Wed, 14 Nov 2007 22:27:00 -0000 [thread overview]
Message-ID: <536096.78475.qm@web56602.mail.re3.yahoo.com> (raw)
In-Reply-To: <20071114132545.GA7892@caradoc.them.org>
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
prev parent reply other threads:[~2007-11-14 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 11:33 Oleg V. Zhylin
2007-11-14 13:25 ` Daniel Jacobowitz
2007-11-14 22:27 ` Oleg V. Zhylin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=536096.78475.qm@web56602.mail.re3.yahoo.com \
--to=ovz@yahoo.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).