[Bug runtime/3718] -c option runs a program but doesn't exit

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

------- Additional Comments From eteo at redhat dot com  2006-12-15 00:41 -------
(In reply to comment #2)
> (In reply to comment #0)
> > [eteo@kerndev profiler]$ /usr/bin/env stap -c gaim poll-select.stp 10000
> >
> > (gaim has ended at this point. it just doesn't stop regardless how many ctrl+c I
> > used)
> > [1]+  Stopped                 ./profiler.sh -s poll-select.stp -d 10000 -c gaim
> 
> Why do you think gaim has exited when it says "stopped" for status?  What is
> "profiler.sh"? Does "ps aux | grep gaim" show anything?

I should be clearer.

To reproduce the problem, type:
stap -c gaim -o log -e 'probe syscall.poll { log(argstr) }'

When gaim is running, click Buddies from the menu, and then Quit. You will find
that you are unable to halt stap/staprun/rmmod.

Some programs work, some doesn't. I tried vpngui, it works all the time, I tried
Thunderbird, it works sometimes (File -> Quit, but not Alt+F4). I have not check
the exit code of these programs, but I am sure that it has stopped running after
I quit these programs.

I am trying to walkthrough these as a potential end-user.

What you see below are what I tried to do to stop stap/staprun/rmmod.

> > [eteo@kerndev profiler]$ killall -9 stap
> > [eteo@kerndev profiler]$ sudo killall -9 staprun
> > [eteo@kerndev profiler]$ ps aux | grep stap
> > eteo      7127  1.6  0.0      0     0 pts/6    Z    20:51   0:00 [stap]
<defunct>
> > root      7249  0.0  0.0   1488   212 pts/6    D    20:51   0:00 /sbin/rmmod -w
> > stap_7127.ko
> 
> Hmmm. Whay is stap zombied? Where is it's parent? 
> 
> > poll-select.stp is a simple stp script that runs for 10000ms, and exit.
> 
> Does the same thing happen with other scripts?
> 
> I cannot reproduce this and reading through the code doesn't immediately reveal
> any places where staprun fails to receive SIGCHLD.  
> 
> 

-- 


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

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