From: Daniel Jacobowitz <drow@false.org>
To: John Breitenbach <breiten@lexmark.com>
Cc: gdb@sourceware.org
Subject: Re: gdb-6.6/ARM/static linking/pthreads
Date: Tue, 28 Aug 2007 18:16:00 -0000 [thread overview]
Message-ID: <20070828181607.GA30544@caradoc.them.org> (raw)
In-Reply-To: <46D462BD.2020201@lpdev.prtdev.lexmark.com>
On Tue, Aug 28, 2007 at 02:00:29PM -0400, John Breitenbach wrote:
> Hi,
> I've got a statically linked application with a dozen or so pthreads (nptl in
> glibc-2.3.6), and want to use gdb to debug it. With gdbserver, I attach to the
> specific thread id, and can set a breakpoint. However, if that breakpoint is
> hit by another of the pthreads, my kernel kills off all of them.
You need both gdb and glibc patches to debug a statically linked
application with pthreads. You can find them in the respective list
archives (gdb-patches and libc-alpha) earlier this year. CVS
snapshots of both GDB and glibc trunk should work; the glibc patch
probably applies cleanly to glibc 2.3.6.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-08-28 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 18:06 John Breitenbach
2007-08-28 18:16 ` Daniel Jacobowitz [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=20070828181607.GA30544@caradoc.them.org \
--to=drow@false.org \
--cc=breiten@lexmark.com \
--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