Date: Thu, 27 Jun 1996 11:25:19 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: alk@Think.COM (Tony Kimball) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG Subject: Re: longstanding, woeful inadeqacy Message-ID: <199606271825.LAA05432@phaeton.artisoft.com> In-Reply-To: <199606270638.BAA00387@compound.Think.COM> from "Tony Kimball" at Jun 27, 96 01:38:17 am
next in thread | previous in thread | raw e-mail | index | archive | help
> Quoth Jordan K. Hubbard on Wed, 26 June: > : Fork is an easier case since you don't need to swap the debugger's > : executable out - just attach to the new process. > > Easier in what sense? It is essentially impossible to debug anything > that forks, since by the time you can attach to it, it has gone > veering wildly out of control. DEFINITION: A process that forks while the "fork debug" flag is set will produces a "debug suspended" forked image instead of a running forked image. The debugger is expected to resume the process if it has set the "fork debug" flag on the parent process of the fork. Trivial. Same for exec. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606271825.LAA05432>