This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: systemtap bug #6500 fallout


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]