Message-ID: <4FA2F20D.3070005@cs.utoronto.ca>
Date: Thu, 03 May 2012 17:01:01 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Short gdb question.
References: <4FA31928.9030200@cfl.rr.com>
In-Reply-To: <4FA31928.9030200@cfl.rr.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 03/05/2012 7:47 PM, eric_justin_allan@cfl.rr.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.
>
> Program received signal SIGABRT, Aborted.
> 0x7ffe0304 in ?? ()
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.

For SIGSEGV (usually an unintentional error), gdb usually does the right 
thing and gives you the offending stack trace.

Ryan


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple