From owner-freebsd-hackers Thu Mar 9 13:58:52 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA23660 for hackers-outgoing; Thu, 9 Mar 1995 13:58:52 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA23652; Thu, 9 Mar 1995 13:58:43 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id PAA26631; Thu, 9 Mar 1995 15:02:11 -0700 Date: Thu, 9 Mar 1995 15:02:11 -0700 From: Nate Williams Message-Id: <199503092202.PAA26631@trout.sri.MT.net> In-Reply-To: Dave Waddell "Re: Stack trace routine for running programs" (Mar 9, 3:44pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Dave Waddell Subject: Re: Stack trace routine for running programs Cc: current@FreeBSD.org, hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk > I don't know whether or not this would work but you might try running > the program to where you want the trace then attaching to the program > with the gnu debugger (it allows attaching to a running program). On certain OS's, but not on SCO or SunOS 4. They are too old for that feature to work. It works on newer BSD systems, and systems based on SVR4, but not on the old beats I have here. Thanks, Nate