This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: backtrace/2447: Cannot produce backtraces for Cygwin programs
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 14 Apr 2008 20:08:01 -0000
- Subject: Re: backtrace/2447: Cannot produce backtraces for Cygwin programs
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR backtrace/2447; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: jim@jimrandomh.org
Cc: gdb-gnats@sources.redhat.com
Subject: Re: backtrace/2447: Cannot produce backtraces for Cygwin programs
Date: Mon, 14 Apr 2008 16:03:01 -0400
On Mon, Apr 14, 2008 at 07:25:36PM -0000, jim@jimrandomh.org wrote:
> Under Cygwin, GDB produces incorrect backtraces whenever a C or C++
> program calls abort(), either directly or by calling assert(0),
> throwing a C++ exception which is not caught, or free()ing the same
> pointer or twice. This makes it pretty useless, since these are the
> majority of crashes.
Thanks for the report. Unfortunately improving backtraces
through the MS DLLs is a very hard project, that so far no one
has been able to solve for GDB.
--
Daniel Jacobowitz
CodeSourcery