From owner-freebsd-hackers Fri May 24 08:13:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA16697 for hackers-outgoing; Fri, 24 May 1996 08:13:28 -0700 (PDT) Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA16683 for ; Fri, 24 May 1996 08:13:20 -0700 (PDT) Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA04102; Fri, 24 May 96 15:12:51 GMT Message-Id: <9605241512.AA04102@fslg8.fsl.noaa.gov> Received: by emu.fsl.noaa.gov (1.40.112.3/16.2) id AA206860769; Fri, 24 May 1996 09:12:50 -0600 Date: Fri, 24 May 1996 09:12:50 -0600 From: Sean Kelly To: grog@lemis.de Cc: msmith@atrad.adelaide.edu.au, archie@whistle.com, freebsd-hackers@freebsd.org In-Reply-To: <199605241004.MAA08611@allegro.lemis.de> (grog@lemis.de) Subject: Re: stack trace library? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Greg" == Greg Lehey 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. 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. -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/