Message-Id:	<200506290857.j5T8vbPe003866@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From:	"Kris Thielemans" <kris DOT thielemans AT imperial DOT ac DOT uk>
To:	"Gnuwin" <cygwin AT cygwin DOT com>
Cc:	"'Kris Thielemans'" <kris DOT thielemans AT csc DOT mrc DOT ac DOT uk>
Subject:	Gdb and stopping at assert or segmentation faults
Date:	Wed, 29 Jun 2005 09:57:33 +0100
MIME-Version:	1.0

Hi

I need to debug a program that throws up an assert(). On Linux, I'm used to
be able to run the program in gdb, and when the assert happens, the program
stops (in the assert function) and I can do a back trace (e.g. info stack).
On cygwin on the other hand, I just get the assert message, and then gdb
says "Program exited normally". No backtrace possible.

The same difference in behaviour between Linux and cygwin with segmentation
faults. It would be incredibly useful to be able to see where the
segmentation fault happened after the crash.

Anyone knows how to change this behaviour on cygwin?

Many thanks

Kris Thielemans
Hammersmith Imanet Ltd

PS: please reply-all such that I get your reply directly in my box as I read
this list via the mail archive.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -