Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 21 Sep 2000 15:54:00 +0400
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin AT sources DOT redhat DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <54142266919.20000921155400@logos-m.ru>
To: "Dehmel, Ruediger" <de AT lmnet DOT de>
CC: cygwin <cygwin AT sources DOT redhat DOT com>
Subject: Re: Where is the core file?
In-reply-To: <A6E475D77D25D311AD91005004066440C837@exserver.lmnet.de>
References: <A6E475D77D25D311AD91005004066440C837 AT exserver DOT lmnet DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Hi!

Thursday, 21 September, 2000 "Dehmel, Rüdiger" de AT lmnet DOT 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 AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com