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:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Gdb and stopping at assert or segmentation faults
Date:	Wed, 29 Jun 2005 18:01:03 +0100
MIME-Version:	1.0
In-Reply-To:	<018501c57cc6$fc349340$0d0a10ac@bach>
Message-ID:	<SERRANOvgntdb2HVZSO000002bf@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Kris Thielemans
>Sent: 29 June 2005 17:24


> 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


  Odd, I would have thought this should work.

  Anyway, "break __assert" works for catching the assertions.  Dunno what's
up with the SEGVs.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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