From owner-freebsd-hackers  Fri May 24 11:14:16 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA12723
          for hackers-outgoing; Fri, 24 May 1996 11:14:16 -0700 (PDT)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12701
          for <hackers@freebsd.org>; Fri, 24 May 1996 11:14:08 -0700 (PDT)
Received: from allegro.lemis.de by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0uN1Jv-000QYYC; Fri, 24 May 96 20:10 MET DST
From: grog@lemis.de (Greg Lehey)
Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax:   +49-6637-919122
Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) 
	id RAA24132; Fri, 24 May 1996 17:32:19 +0200
Message-Id: <199605241532.RAA24132@allegro.lemis.de>
Subject: Re: stack trace library?
To: kelly@fsl.noaa.gov (Sean Kelly)
Date: Fri, 24 May 1996 17:32:18 +0200 (MET DST)
Cc: hackers@freebsd.org (FreeBSD Hackers)
In-Reply-To: <9605241512.AA04102@fslg8.fsl.noaa.gov> from "Sean Kelly" at May 24, 96 09:12:50 am
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Sean Kelly writes:
>
>>>>>> "Greg" == Greg Lehey <grog@lemis.de> writes:
>
>     Greg> What do people think?  I could hack up a prototype pretty
>     Greg> quickly if there's enough interest (and no show-stopping
>     Greg> conceptual problems).
>
> Sounds more complex than I'd ever need.

Depends on what you need, I suppose.

> One nice feature of HP/UX of which I make nearly daily use:
>
> 	extern void U_STACK_TRACE();
>
> which dumps the call stack to standard error.  There's also a stack
> trace library for traversing the call stack and getting various bits
> of info.

If it's there, that's fine.  A good stack trace should also show you
parameters and line numbers, and that's non-trivial.  Going into a
debugger would be comparatively easy, and it offers a whole lot more
in addition (including, as Mike says, stack trace and exit).

Greg