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: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 10 Jul 2008 17:04:28 -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 fche at redhat dot com 2008-07-10 17:04 -------
(In reply to comment #9)
> 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.
Could you use kill (SIGTERM, - stap_pid) so you broadcast the signal
to the process group?
> 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?.
I'm not sure that is legal from within a signal handler proper, but as a
part of stap's exit, one could do a kill (SIGTERM, 0)
--
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.