Date: Fri, 24 May 1996 17:32:18 +0200 (MET DST) From: grog@lemis.de (Greg Lehey) To: kelly@fsl.noaa.gov (Sean Kelly) Cc: hackers@freebsd.org (FreeBSD Hackers) Subject: Re: stack trace library? Message-ID: <199605241532.RAA24132@allegro.lemis.de> In-Reply-To: <9605241512.AA04102@fslg8.fsl.noaa.gov> from "Sean Kelly" at May 24, 96 09:12:50 am
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605241532.RAA24132>