From owner-freebsd-hackers  Wed Jun 26 19:33:49 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA14099
          for hackers-outgoing; Wed, 26 Jun 1996 19:33:49 -0700 (PDT)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA14091
          for <hackers@freebsd.org>; Wed, 26 Jun 1996 19:33:46 -0700 (PDT)
Received: from Early-Bird-1.Think.COM by mail.think.com; Wed, 26 Jun 96 22:11:58 -0400
Received: from compound.Think.COM by Early-Bird.Think.COM; Wed, 26 Jun 96 22:33:17 EDT
Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id VAA02519; Wed, 26 Jun 1996 21:36:19 -0500 (CDT)
Date: Wed, 26 Jun 1996 21:36:19 -0500 (CDT)
From: Tony Kimball <alk@Think.COM>
Message-Id: <199606270236.VAA02519@compound.Think.COM>
To: jkh@time.cdrom.com
Cc: hackers@freebsd.org
Subject: Re: longstanding, woeful inadeqacy 
References: <199606270008.TAA28833@compound.Think.COM>
	<28552.835835464@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Quoth Jordan K. Hubbard on Wed, 26 June:
: I think it's something that'd be far more trouble that it's worth
: to "fix" - why not just debug the binary being exec'd if that's the
: issue?

Similarly, fork.  

The reason why you would want to debug through the exec is
to debug in the correct environment.  fork is perhaps a more
compelling case?