Re: gdb/610: gdb crashes when listing source of g++-3.1-compiled binary

[Daniel Jacobowitz <drow at mvista dot com>]

The following reply was made to PR gdb/610; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: rohlfing@stanford.edu
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/610: gdb crashes when listing source of g++-3.1-compiled binary
Date: Thu, 18 Jul 2002 14:21:11 -0400

 On Thu, Jul 18, 2002 at 06:11:44PM -0000, rohlfing@stanford.edu wrote:
 > 
 > >Number:         610
 > >Category:       gdb
 > >Synopsis:       gdb crashes when listing source of g++-3.1-compiled binary
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Thu Jul 18 11:18:00 PDT 2002
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     rohlfing@stanford.edu
 > >Release:        gdb+dejagnu-20020717
 > >Organization:
 > >Environment:
 > Solaris7 (SPARC), gcc/g++ 3.1
 > >Description:
 > When dealing with "complex" binaries generated by g++ 3.1, 
 > gdb crashes as early as just starting up and issuing "list".
 > 
 > The crash occurs at buildsym.c:309, where "ftype" (the "type"
 > element of "symbol" is sometimes NULL, sometimes another
 > invalid pointer.
 > >How-To-Repeat:
 > This problem is very hard to reproduce without sending in
 > a multi-1000-line project. Sorry, but I also don't understand
 > enough of gdb's internal data structures to give a better
 > hint as to what goes wrong.
 
 I've never seen this crash, so we need more information.  Can you at
 least provide a backtrace?
 
 -- 
 Daniel Jacobowitz                           Carnegie Mellon University
 MontaVista Software                         Debian GNU/Linux Developer