This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: systemtap bug #6500 fallout
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: David Smith <dsmith at redhat dot com>
- Cc: Ananth Mavinakayanahalli <ananth at in dot ibm dot com>, Systemtap List <systemtap at sources dot redhat dot com>
- Date: Mon, 12 May 2008 16:23:50 -0400
- Subject: Re: systemtap bug #6500 fallout
- References: <4828946E.8070605@redhat.com> <y0m1w478ga6.fsf@ton.toronto.redhat.com>
I wrote:
>> [...]
>> So, my tentative plan is to have the task finder layer call the callback
>> (potentially) twice when an exec happens - once to unregister the "old"
>> path and once to register the "new" path.
>
> Yeah, that makes sense. Further, since an "exec" is a process-wide
> event, so I'd expect death notifications for all threads other than
> the caller. An "exit" is also process-wide; I presume the per-thread
> death notifications work there already. [...]
By the way, this does not really mean that all those peer-thread death
notifications should be exposed at the systemtap script level. If the
probe point says "process().exec" or "process().death", then one could
construe that as only a single process-level notification being
requested. (Then how to receive a notification about each individual
thread terminating? A new probe point perhaps; or maybe it already
shows up under process("...").syscall?)
- FChE