Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Mon, 3 Feb 2003 11:22:29 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Gerrit Cap <Gerrit DOT Cap AT marble DOT be>
cc: cygwin AT cygwin DOT com
Subject: Re: Analysing a stackdump file
In-Reply-To: <5.1.1.5.2.20030203090917.00b86778@www.marble.be>
Message-ID: <Pine.GSO.4.44.0302031120180.24195-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 3 Feb 2003, Gerrit Cap wrote:

> Hello
>
> 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 ?
>
> Gerrit.

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>.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT 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!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/