> > IMHO, I think it should work just like it does now. ?I don't want the D > > program that is monitoring my process to have that kind of control, > > unless I specifically tell it to do so. ?What if I'm only interested in > > monitoring the first part of the execution? > > Note that this only applies to commands that have been spawned by > dtrace(1M) via -c, not existing processes that we've attached to with > -p. The kill-on-last-close flag would apply for -c, and the > release-on-last-close flag would apply for -p. > > BTW, for a good demonstration of how annoying this bug can be, run > "dtrace -n jarod -c prstat".
The process should be killed: this is a (dumb) bug in my code. If something is attached to by a debugger, the default behavior should be to release it and set it running again. If something is created by the debugger, the default behavior should be to kill it if the debugger exits. This is how all p-tools, truss, mdb, etc. all behave. -Mike -- Mike Shapiro, Sun Microsystems Fishworks. blogs.sun.com/mws/
_______________________________________________ dtrace-discuss mailing list [email protected]
