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
To: cygwin@cygwin.com
From: Kris Thielemans <kris.thielemans@csc.mrc.ac.uk>
Subject:  Re: Gdb and stopping at assert or segmentation faults
Date: Tue, 5 Jul 2005 23:19:24 +0000 (UTC)
Lines: 40
Message-ID:  <loom.20050706T011317-321@post.gmane.org>
References:  <018501c57cc6$fc349340$0d0a10ac@bach> <SERRANOvgntdb2HVZSO000002bf@SERRANO.CAM.ARTIMI.COM> <loom.20050630T153623-426@post.gmane.org>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Hi all

> 
> Dave Korn <dave.korn <at> artimi.com> writes:
> 
> > > 
> >   Anyway, "break __assert" works for catching the assertions.  Dunno what's
> > up with the SEGVs.
> > 

well, it turns out Dave's suggestion doesn't work anymore on latest cygwin 
(tested this only with C++ programs):
GNU gdb 6.3.50_2004-12-28-cvs (cygwin-special)
gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)

In fact, it will now break before entering main(), but not when the assert is 
called.

Using "break __assert" says
(gdb) break __assert
Breakpoint 1 at 0x4ac3e6: file /usr/lib/gcc/i686-pc-
cygwin/3.4.4/include/c++/iostream, line 77.
(gdb) r 
Starting program: /home/kris/MyDocuments/mytest.exe

Breakpoint 1, __static_initialization_and_destruction_0 (__initialize_p=1, 
    __priority=65535)
    at /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/iostream:77
(gdb) c
assertion "overlap>-epsilon" failed: 
file "./include/stir/numerics/overlap_interpolate.inl", line 108

Program exited normally.

Any other suggestions?

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/