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]

[Bug tapsets/12413] New: kprocess.* support PIDs but not TIDs


http://sourceware.org/bugzilla/show_bug.cgi?id=12413

           Summary: kprocess.* support PIDs but not TIDs
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap@sources.redhat.com
        ReportedBy: jan.kratochvil@redhat.com


Created attachment 5201
  --> http://sourceware.org/bugzilla/attachment.cgi?id=5201
untested fix

One cannot provide thread-specific tracing this way.
I had to call task_tid(task) in the .stp script.

Also while kprocess.create differentiates current context from the created
process by >new_<pid kprocess.release uses just plain pid, not >released_<pid,
despite the context may be different from the released task.  I found it a bit
non-systematic.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


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