From: John Breitenbach <breiten@lexmark.com>
To: gdb@sourceware.org
Subject: gdb-6.6/ARM/static linking/pthreads
Date: Tue, 28 Aug 2007 18:06:00 -0000 [thread overview]
Message-ID: <46D462BD.2020201@lpdev.prtdev.lexmark.com> (raw)
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.
We had some code in the linux kernel in the past which would insert and
remove breakpoints on context switches, and I'd like to know if that
needs to get propagated with our kernel upgrade (to 2.6.18) or is there
a better way. Can gdbserver find out about the other threads, and
handle the automatic continue if the SIGTRAP is for the wrong process.
Or can I do something in the kernel to remove the breakpoint,
single-step and restore the breakpoint in the case of the wrong process id?
Thanks in advance for any advice
John
next reply other threads:[~2007-08-28 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 18:06 John Breitenbach [this message]
2007-08-28 18:16 ` Daniel Jacobowitz
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=46D462BD.2020201@lpdev.prtdev.lexmark.com \
--to=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