Delivered-To:	listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<000b01be5935$b1122e10$1b108ece@np_home_pc>
From:	"Nirmal Prasad" <nprasad AT truept DOT com>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	b20 gdb problem.. (abort() somewhere)
Date:	Mon, 15 Feb 1999 17:51:13 -0500
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3110.3

hi there,

This is with reference to my previous mail asking help on GDB and i finally
found that the signal that gdb was getting was SIGABRT if
($INCLUDE/sys/signals.h) is okay and this causes gdb to terminate the
application. There is no indication as to who is throwing the abort(). It
might be either in gdb or in the standard run-time libraries. There is no
information that i am able to get as to which module has called abort. My
application does not have any aborts and i have used exception handling in
most of the cases. Any pointers as to how to solve this ???? besides opening
up the code for gdb and the run-time libraries to find out who has called
abort(). Furthermore as the application runs fine outside of GDB the abort()
is most likely inside GDB or that there is something wierd that GDB is doing
that is causing an abort() somewhere. But the funny thing is that after  the
application aborts i can see the GDB  prompt.

Thanks in advance

Regards

Nirmal Prasad R.

- Raw text -