From: "Dave Korn" <dk@artimi.com>
To: "'Craig Jeffree'" <craig.jeffree@preston.net>
Cc: "'Fabian Cenedese'" <Cenedese@indel.ch>, <gdb@sources.redhat.com>
Subject: RE: gdb 6.1.1 (PPC) crash (long) AND gdb crash in cp_print_class_method
Date: Tue, 07 Sep 2004 14:41:00 -0000 [thread overview]
Message-ID: <NUTMEGkg3nOpj53XaDF000011e5@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <1094165275.32298.130.camel@cosmo.preston.net>
> -----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....
next prev parent reply other threads:[~2004-09-07 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 9:01 gdb 6.1.1 (PPC) crash (long) Fabian Cenedese
2004-09-01 9:18 ` Fabian Cenedese
2004-09-02 12:20 ` gdb 6.1.1 (PPC) crash (long) AND gdb crash in cp_print_class_method Dave Korn
2004-09-02 12:59 ` Fabian Cenedese
2004-09-02 14:07 ` Dave Korn
2004-09-02 22:48 ` Craig Jeffree
2004-09-07 14:41 ` Dave Korn [this message]
2004-09-02 11:59 ` gdb 6.1.1 (PPC) crash (long) Fabian Cenedese
2004-09-07 14:50 ` Daniel Jacobowitz
[not found] ` <5.2.0.9.1.20040907170934.01d457f8@NT_SERVER>
2004-09-07 17:02 ` Daniel Jacobowitz
2004-09-29 5:27 ` Craig Jeffree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NUTMEGkg3nOpj53XaDF000011e5@NUTMEG.CAM.ARTIMI.COM \
--to=dk@artimi.com \
--cc=Cenedese@indel.ch \
--cc=craig.jeffree@preston.net \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox