Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: Jason Merrill <jason@redhat.com>, Daniel Berlin <dberlin@redhat.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, <gdb-patches@sources.redhat.com>
Subject: Re: GDB PATCH to disable specific G++ demangling
Date: Tue, 19 Dec 2000 08:44:00 -0000	[thread overview]
Message-ID: <B664FA55.82B%dan@cgsoftware.com> (raw)
In-Reply-To: <u9y9xciv1g.fsf@casey.cambridge.redhat.com>

On 12/19/00 9:37 AM, "Jason Merrill" <jason@redhat.com> wrote:

>>>>>> "Daniel" == Daniel Berlin <dberlin@redhat.com> writes:
> 
>>> 
>>> Could you possibly say a few words about this change, and what exactly
>>> is its effect, for those who don't know by heart what AUTO_DEMANGLING
>>> does?
> 
>> AUTO_DEMANGLING detects the mangling style automatically, and demangles it
>> based on that.
>> This change defaults to doing this, now that we have two very different
>> demangling styles about to common usage, and we previously defaulted to
>> assuming we had one of these styles (the old abi mangling) if we
>> determined it was a gcc compiled program, and we were using dwarf or
>> stabs.
> 
> Yup.
> 
>> I would have fixed this before, but i mainly deal with dwarf2, which we
>> default to AUTO_DEMANGLING.
> 
> Hmm, so do I, and I was still seeing mangled names before this patch.  I
> assumed that the dwarf2 code was using something out of stabsread, but
> didn't bother tracking it down.

Hmmm. I bet your libstdc++ or something had STABS debug info in it, which
would result in executables with both stabs, and dwarf2, and exhibit the
problem.



> 
> So, OK?

As far as I am concerned, as C++ support maintainer, but it's not my call. I
believe Jim Blandy is the STABS/DWARF2 reader person, without the
MAINTAINERS file sitting in front of me.

--Dan


      reply	other threads:[~2000-12-19  8:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10012180337180.15723-100000@www.cgsoftware.com>
2000-12-19  6:39 ` Jason Merrill
2000-12-19  8:44   ` Daniel Berlin [this message]

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=B664FA55.82B%dan@cgsoftware.com \
    --to=dan@cgsoftware.com \
    --cc=dberlin@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jason@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