From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/9925] task_execname(task) incorrect in process.create
Date: Thu, 05 Mar 2009 17:37:00 -0000 [thread overview]
Message-ID: <20090305172214.26536.qmail@sourceware.org> (raw)
In-Reply-To: <20090305162902.9925.cap@nsc.liu.se>
------- Additional Comments From dsmith at redhat dot com 2009-03-05 17:22 -------
(In reply to comment #3)
> (In reply to comment #1)
> > The output is "correct"
>
> It may be expected (given what process.create really is) but it is not
> "correct". That however can be fixed by updating the documentation...
Which part of the documentation do you object to?
> The "task" in process.create is half the new process and half the old. I fear
> this will confuse people even if the documentation/manpage is updated.
I have to disagree with you - the "task" in process.create is fully the new
process. Since the exec hasn't happened yet, execname is still that of the
parent, which is correct. Remember that We have no guarantees that the new
process will do an exec at all - in the case of multi-threaded programs, this is
usually the case.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=9925
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-03-05 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 17:02 [Bug tapsets/9925] New: " cap at nsc dot liu dot se
2009-03-05 17:05 ` [Bug tapsets/9925] " mjw at redhat dot com
2009-03-05 17:22 ` cap at nsc dot liu dot se
2009-03-05 17:32 ` cap at nsc dot liu dot se
2009-03-05 17:37 ` dsmith at redhat dot com [this message]
2009-03-06 1:28 ` jistone at redhat dot com
2009-03-06 8:19 ` jistone at redhat dot com
2009-03-06 9:18 ` wenji dot huang at oracle dot com
2009-03-06 14:18 ` cap at nsc dot liu dot se
2009-03-06 14:27 ` dsmith at redhat dot com
2009-03-15 16:44 ` jistone at redhat dot com
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=20090305172214.26536.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).