This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Where is the core file?
- To: "Dehmel, Ruediger" <de at lmnet dot de>
- Subject: Re: Where is the core file?
- From: Egor Duda <deo at logos-m dot ru>
- Date: Thu, 21 Sep 2000 15:54:00 +0400
- CC: cygwin <cygwin at sources dot redhat dot com>
- Organization: DEO
- References: <A6E475D77D25D311AD91005004066440C837@exserver.lmnet.de>
- Reply-To: Egor Duda <cygwin at sources dot redhat dot com>
Hi!
Thursday, 21 September, 2000 "Dehmel, Rüdiger" de@lmnet.de wrote:
DR> I get the mesage: .... core dumped ....
DR> but there is no core file, only a ...exe.stackdump
DR> How to find the bug with gdb?
you have several possibilities:
1. just run your program under gdb -- "gdb bad-program.exe". when you
program crashes, gdb will stop it an show you the place where
exception occurred.
2. add "error_start=c:\path\to\gdb\gdb.exe" to CYGWIN environment
variable. this turns on the jit-debug facility in cygwin. when you
program encounter exception, cygwin will automatically invoke
gdb and instructs it to attach to crashed process.
3. build "dumper" utility. it's in current cvs sources of cygwin.
then, if you add "error_start=c:\path\to\dumper\utility\dumper.exe" to
CYGWIN env. variable, dumper.exe will be started in case of
exception, and it'll create bad-brogram.exe.core. This core file can
be analyzed with "gdb --core=bad-brogram.exe.core". NOTE: you'll need
latest sources of gdb, bfd, and cygwin from sourceware cvs to do this.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com