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 17:44:51 -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 17:44 -------
(In reply to comment #10)
> Could you use kill (SIGTERM, - stap_pid) so you broadcast the signal
> to the process group?
I tried with kill(SIGTERM,0) and pkill SIGTERM -g getpgid(0), both seem to work
fine. I was not sure if there was any design reason behind not passing on the
signals. Your reply answers that question :).
There is a second part to this problem, in that i'm having to kill the stap
process twice from my program to exit. This is due to the pending_interrupts > 1
check. This is not really a major bother but it would be nice if we didnt have
to send two signals. Do you think it would be ok to remove this check
(pending_interrupts > 1) if the execution is currently in pass 5?. It should be
straightforward to modify the code to do so, but again, is there any reason why
we should retain this check after the translation phases are over?.
--
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.