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 uprobes/6841] system-wide utrace syscall tracing script don't respond signal


------- Additional Comments From mhiramat at redhat dot com  2008-08-18 17:44 -------
Created an attachment (id=2913)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=2913&action=view)
signal sending trace logs

Here is a pair of trace logs of stapio's signal handling.

the normal part shows normal behaviour of signal sending.
A SIGINT(2) was sent to stapio and __group_complete_signal()
found stapio's signal thread(2035) and woke it up.
This log also shows signal thread didn't have TIF_SIGPENDING.
 sigthread(2035){.state=1, .blocked=0, .flags=400040, .sigpending=0}

the strange part shows abnormal behaviour of signal sending.
A SIGINT(2) was sent to stapio, but __group_complete_signal()
couldn't find stapio's signal thread(1984) because it had 
TIF_SIGPENDING.
 sigthread(1984){.state=1, .blocked=0, .flags=400040, .sigpending=1}

As far as I can see, signal sending process seems expect that 
signal pending process is already running, not in sleep.

Thank you,

-- 


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

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


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