From: "Douglas Evans" <dje@google.com>
To: gdb@sourceware.org
Subject: Re: linux-thread-db.c not only caller of add_thread, -> gdb segv
Date: Sat, 10 Nov 2007 03:40:00 -0000 [thread overview]
Message-ID: <e394668d0711091940n7ec01450g8b82e5c3163e4690@mail.gmail.com> (raw)
In-Reply-To: <20071110032558.GA19831@caradoc.them.org>
On Nov 9, 2007 7:25 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, Nov 09, 2007 at 05:26:56PM -0800, Douglas Evans wrote:
> > GDB detects the exec and removes thread_db_ops from the target stack.
> > But (a) it doesn't clear out thread_list and (b) still thinks it has control of
> > the running process.
>
> (b) should be true, no?
I suspect it's a matter of degrees (so to speak) or word choice (apologies).
Until MAY_FOLLOW_EXEC is true for linux I'd expect gdb to return control
to the user when an exec() happens.
Am I wrong in thinking gdb will lose control across the exec()?
> Exec support is somewhat horrible. I posted a patch for it recently
> which might help (might not, I'm not sure).
I'll try to find it and give it a try. Thanks.
next prev parent reply other threads:[~2007-11-10 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 4:38 Douglas Evans
2007-11-09 14:02 ` Daniel Jacobowitz
2007-11-10 1:27 ` Douglas Evans
2007-11-10 3:26 ` Daniel Jacobowitz
2007-11-10 3:40 ` Douglas Evans [this message]
2007-11-10 5:20 ` Douglas Evans
2007-11-10 16:00 ` 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=e394668d0711091940n7ec01450g8b82e5c3163e4690@mail.gmail.com \
--to=dje@google.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