This is the mail archive of the
mailing list for the Cygwin project.
Re: Short gdb question.
- From: Ryan Johnson <ryan dot johnson at cs dot utoronto dot ca>
- To: cygwin at cygwin dot com
- Date: Thu, 03 May 2012 17:01:01 -0400
- Subject: Re: Short gdb question.
- References: <4FA31928.firstname.lastname@example.org>
On 03/05/2012 7:47 PM, email@example.com wrote:
Is this the right place to suggest that gdb be upgraded for cygwin. If
not where could I suggest that? If this is an acceptable place then
can I add here that if you guys do upgrade gdb that I was hoping you
could make it a bit more detailed maybe make it to show a bit more
information about crashes. An example is that I m working with a
linked list and when the program crashes gdb prints out and only
prints out the words below this text. I am left clueless about the error.This happens only with SIGABRT, AFAIK. You can work around it by setting
a breakpoint on "_abort" which will catch the problem before the stack
gets lost in windows-land.
Program received signal SIGABRT, Aborted.
0x7ffe0304 in ?? ()
For SIGSEGV (usually an unintentional error), gdb usually does the right
thing and gives you the offending stack trace.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple