This is the mail archive of the
mailing list for the Cygwin project.
Re: Analysing a stackdump file
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Gerrit Cap <Gerrit dot Cap at marble dot be>
- Cc: cygwin at cygwin dot com
- Date: Mon, 3 Feb 2003 11:22:29 -0500 (EST)
- Subject: Re: Analysing a stackdump file
- Reply-to: cygwin at cygwin dot com
On Mon, 3 Feb 2003, Gerrit Cap wrote:
> A few weeks ago I build an xplanet.exe file from the sources (which is now
> being published by Hans Ecke's XPlanet website http://hans.ecke.ws/xplanet
> and he sent me from a user that had a problem resulting in a stackdump
> file. My question is rather simple: the xplanet.exe.stackdump file is
> rather cryptic, how can one analyse that dump file to try to find out why
> it was generated ?
If you have a debug build of xplanet, "man addr2line". You may also want
to read <http://cygwin.com/cygwin-ug-net/using-utils.html#DUMPER>.
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html