From: Daniel Jacobowitz <dan@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>, gdb@sourceware.org
Subject: Re: GDB hangs with simple multi-threaded program on linux
Date: Fri, 16 Jul 2010 15:58:00 -0000 [thread overview]
Message-ID: <20100716155754.GA6315@caradoc.them.org> (raw)
In-Reply-To: <m3bpa8lh4f.fsf@fleche.redhat.com>
On Thu, Jul 15, 2010 at 12:44:32PM -0600, Tom Tromey wrote:
> The approach in this patch seems to be racy. Roland says we can do
> better if we enable exit tracing. I see this in linux-nat.c:
>
> /* Do not enable PTRACE_O_TRACEEXIT until GDB is more prepared to support
> read-only process state. */
>
> I wonder what that means :-)
I meant to use this for "catch exit". But once you reach
PTRACE_O_TRACEEXIT, the process is in a pretty unique state. For
instance, you can't call a function - if you do, the process will exit
as soon as you resume it!
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2010-07-16 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 15:46 Thiago Jung Bauermann
2010-07-15 18:44 ` Tom Tromey
2010-07-15 18:47 ` Tom Tromey
2010-07-15 22:22 ` Thiago Jung Bauermann
2010-07-16 15:58 ` 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=20100716155754.GA6315@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=tromey@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