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 csc DOT mrc DOT ac DOT uk>
To:	"'Brian Dessent'" <brian AT dessent DOT net>
Cc:	"'Gnuwin'" <cygwin AT cygwin DOT com>
Subject:	RE: Gdb and stopping at assert or segmentation faults
Date:	Wed, 29 Jun 2005 17:24:12 +0100
Message-ID:	<018501c57cc6$fc349340$0d0a10ac@bach>
MIME-Version:	1.0
In-Reply-To:	<42C2B809.6C7821A1@dessent.net>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id j5TGP40U018851

Hi Brian

> You need to set the 'error_start' parameter of the CYGWIN 
> environment variable to the (windows) path of gdb.
> 

I think what you're saying is that if I do this, it will launch gdb on the
crash? Ok.

However, what I was saying is that I would like to be able to backtrace when
I launch a program from within gdb:

Gdb myprog
Run
<assert or segmentation fault>
Info stack

> You can also call cygwin_internal (CW_DEBUG_SELF,
> "c:\\path\\to\\gdb.exe") in your code to force a fault.
> 
Ok. That's useful as well. Thanks!

Kris


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