From: Tom Horsley <tom.horsley@ccur.com>
To: linux-kernel@vger.kernel.org
Cc: bugsy@ccur.com
Subject: insufficent ptrace status when a thread calls exec
Date: Wed, 14 Dec 2005 07:20:11 -0500 [thread overview]
Message-ID: <1134562811.25787.10.camel@tweety> (raw)
The redhat folks sent me to the kernel folks with this one:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171323
This bugzilla contains a test program that takes the (admittedly
weird) action of having a thread in a multi-threaded program
call exec() (not fork then exec, just exec :-). When a poor
old debugger is debugging this thing, most of the threads
just up and disappear, the main thread says it is about to
exit, then instead of exiting, it actually execs.
I don't believe there is enough information laying around for
any debugger to deduce what just happened and handle it
correctly. The bugzilla proposes the creation of a new
extended status so the main thread could say "I'm about to
exec on behalf of one of my threads which are all disappearing"
instead of saying "I'm about to exit" (which is a lie).
I certainly don't know enough to figure out how to actually
implement this and propose a patch, but I thought I'd at least
raise the issue with folks who probably know more about ptrace
than I do.
Thanks.
reply other threads:[~2005-12-14 12:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1134562811.25787.10.camel@tweety \
--to=tom.horsley@ccur.com \
--cc=bugsy@ccur.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome