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
Message-Id:	<5.1.1.5.2.20030203090917.00b86778@www.marble.be>
X-Sender:	gerrit AT www DOT marble DOT be
Date:	Mon, 03 Feb 2003 09:12:23 +0100
To:	cygwin AT cygwin DOT com
From:	Gerrit Cap <Gerrit DOT Cap AT marble DOT be>
Subject:	Analysing a stackdump file
Mime-Version:	1.0

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.





--
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/

- Raw text -