🚀 go-pugleaf

>>>>> "Michael" == Michael Schumacher <hightec@sbusol.rz.uni-sb.de> writes:

Michael> I'm not aware of *any* debugger which could trace child
Michael> processes (this has to do with the memory management of the
Michael> underlying OS). The following hack might be helpful if your
Michael> OS allows to attach to running processes: right after the
Michael> fork, put an endless loop which is controlled by a variable,
Michael> i.e.

Debuggers do exist which can do this.  I wish gdb would.

Another useful trick is to swap the parent and child branches of the
if following the fork.  Then the debugger will trace the "child"
instead of the "parent".

And instead of busy-waiting with a while, you should use sigpause.
Connecting to the running process with a debugger will cause the
sigpause to return.

Tom
--
tromey@cns.caltech.edu                Member, League for Programming Freedom
"Sadism and farce are always inexplicably linked"
	-- Alexander Theroux