Messages in this thread | | | From | (Matthias Urlichs) | Subject | Re: Parent process switching on debugger abort in 2.0.3x | Date | 18 Jul 1997 09:46:24 +0200 |
| |
Pavel Machek <pavel@Elf.mj.gts.cz> writes: > > > > Suppose, for instance, you kill your debugger, but the beast has written a > > few breakpoints into the debuggee. What to do? Right -- either you kill the > > child along with the parent (any fatal signal) or it's the debugger's job > > to clean up after itself and properly detach the child (any other > > signal). > > Well, and when I kill debugger with -9?
Killing programs with -9 means that you, the killer, assume any and all responsibility for kruft the killee has not been able to clean up.
Telling the kernel that you have cleaned up is easy, you clear the traced flag. If you didn't, well...
I agree, of course, that reparenting the debuggee to PID 1 because the debugger gets killed is the worst possible way of handling the problem.
-- Matthias Urlichs
| |