This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded
- From: "anithra at linux dot vnet dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 10 Jul 2008 16:43:55 -0000
- Subject: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded
- References: <20080404085514.6030.ananth@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From anithra at linux dot vnet dot ibm dot com 2008-07-10 16:43 -------
The signal(SIG_CHLD, SIG_IGN) would result in the STAP process ignoring the
SIG_CHLD signal. Wont this result in the stap process running forever, waiting
for an explicit signal?. In case of the stapgui i want to terminate the stap
process, and along with it the stapio process.
Eg:
root 28391 24712 3 20:51 pts/1 00:00:00 stap /counter.stp
root 28595 28391 11 20:51 pts/1
00:00:00/usr/local/libexec/systemtap/stapio
/tmp/stap5z1Ybp/stap_eab4dea519753fb568fa80466b98c4e3_240.ko
Now if i 'kill -SIGTERM 28391', that stops the stap process, but leaves 28595
running as the signal is not passed to the child.
If any tool/application wishes to invoke systemtap through a program or as part
of a script , the script would only have the process id of the immediate child
forked, in this case the stap process. It would not be able to terminate the
process & unload the module correctly. This is the problem i have with the stapgui.
I was planning to change stap's signal handler to pass the signal to the
process group before exiting. Is there any reason why we would not want to do
that?.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6030
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.