From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: gdb/threading under arm-linux
Date: Wed, 13 Mar 2002 09:09:00 -0000 [thread overview]
Message-ID: <20020313120947.A12715@nevyn.them.org> (raw)
In-Reply-To: <aeb594164b.miah@picsel.com>
On Wed, Mar 13, 2002 at 01:11:57PM +0000, Miah Gregory wrote:
> In message <20020306110033.A14410@nevyn.them.org>
> Daniel Jacobowitz <dmj+@andrew.cmu.edu> wrote:
>
> > On Wed, Mar 06, 2002 at 09:45:15AM +0000, Miah Gregory wrote:
> > > In message <20020305103521.A27860@nevyn.them.org>
> > > Daniel Jacobowitz <drow@mvista.com> wrote:
>
> -snip-
>
> > > > Please try a current snapshot (see http://sources.redhat.com/gdb/).
> > > > It should work.
>
> > > No luck. Now both kernels give the SIG32 problem.
>
> > You almost certainly do not have libthread_db.so.1 in /lib. You need
> > that to debug threads.
>
> Ok, I managed to build enough of libc 2.2.3 in order to get the required
> libthread_db.so.1 library, and I then installed that in /lib.
>
> With the 20020305 snapshot, I get all the same problems. Is there a simple
> way to find out whether gdb is trying to use that library?
I recommend running gdb within gdb, and breakpointing on
thread_db_load.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-13 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 5:39 Miah Gregory
2002-03-05 7:35 ` Daniel Jacobowitz
2002-03-06 1:45 ` Miah Gregory
2002-03-06 1:51 ` Miah Gregory
2002-03-06 17:32 ` Michael Snyder
2002-03-13 5:13 ` Miah Gregory
[not found] ` <20020306110033.A14410@nevyn.them.org>
2002-03-13 5:12 ` Miah Gregory
2002-03-13 9:09 ` Daniel Jacobowitz [this message]
2002-03-13 9:44 ` Miah Gregory
2002-03-13 9:50 ` Daniel Jacobowitz
2002-03-13 9:36 ` Kevin Buettner
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=20020313120947.A12715@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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