This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: gdb 6.1.1 (PPC) crash (long) AND gdb crash in cp_print_class_method
- From: "Dave Korn" <dk at artimi dot com>
- To: "'Craig Jeffree'" <craig dot jeffree at preston dot net>
- Cc: "'Fabian Cenedese'" <Cenedese at indel dot ch>,<gdb at sources dot redhat dot com>
- Date: Tue, 7 Sep 2004 15:39:13 +0100
- Subject: RE: gdb 6.1.1 (PPC) crash (long) AND gdb crash in cp_print_class_method
> -----Original Message-----
> From: Craig Jeffree
> Sent: 02 September 2004 23:48
> To: Dave Korn
> Cc: 'Fabian Cenedese'; gdb
> Subject: RE: gdb 6.1.1 (PPC) crash (long) AND gdb crash in
> cp_print_class_method
>
> On Fri, 2004-09-03 at 00:05, Dave Korn wrote:
> > Or perhaps as a consequence of the C++ ABI changes
> between gcc 2.9x and
> > gcc 3.x, or recent improvements and upgrading of dwarf handling.
> >
> > Craig, is your code also compiled using an old gcc 2.95
> as well, by any
> > chance?
> >
>
> Yes. 2.95.3 infact.
>
> Cheers,
> Craig.
OK, we have our suspect then: some kind of backward incompatibility
between gdb-6.x (which is sync'ed with gcc-3.x) and the objects compiled by
gcc-2.x, and it is most likely to be caused by either a change in the
name-mangling relating to the new C++ ABI in series 3 gcc, or a change in
the debug info format.
I'm not too familiar with the internals here, so my first recommendation
to both of you would be to revert to a 5.x gdb, which was the contemporary
version to 2.95, and as Fabian has already observed seems to handle the
object files in question without any problem.
cheers,
DaveK
--
Can't think of a witty .sigline today....