Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
From: "Kris Thielemans" <kris.thielemans@csc.mrc.ac.uk>
To: "'Brian Dessent'" <brian@dessent.net>
Cc: "'Gnuwin'" <cygwin@cygwin.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
Content-Type: text/plain; 	charset="us-ascii"
In-Reply-To: <42C2B809.6C7821A1@dessent.net>
Content-Transfer-Encoding: 8bit
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/