This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GDB PATCH to disable specific G++ demangling


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]