[Bug lket/3536] New: lket does not trace the right pid and appname

["eteo at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

If you perform the following two one-liner scripts, it will not give similar
trace results:

(1) stap -p2 -bM -e 'probe addevent.iosyscall.open {}' 
(2) stap -ve 'probe syscall.open { printf("%s(%d): %s\n", execname(), pid(),
argstr)} '

outputs:
(1) 9.302127 CPU:0 PID:2399 APPNAME:(null) EVT_NAME:iosyscall.open.entry
filename:/dev/bus/usb/002/001,flags:2,mode:1,
9.302163 CPU:0 PID:2399 APPNAME:(null) EVT_NAME:iosyscall.open.entry
filename:/dev/bus/usb/002/003,flags:2,mode:1,
(2) pcscd(2395): "/dev/bus/usb/002/001", O_RDWR
pcscd(2395): "/dev/bus/usb/002/003", O_RDWR

Looks like the pid from the lket trace refers to tid(). APPNAME is pcscd but
it's displayed as (null).

-- 
           Summary: lket does not trace the right pid and appname
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P2
         Component: lket
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: eteo at redhat dot com


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.