This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: GDB PATCH to disable specific G++ demangling
- To: dberlin at redhat dot com
- Subject: Re: GDB PATCH to disable specific G++ demangling
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Tue, 19 Dec 2000 06:20:21 -0500 (EST)
- CC: jason at redhat dot com, gdb-patches at sources dot redhat dot com
- References: <Pine.LNX.4.10.10012180337180.15723-100000@www.cgsoftware.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Mon, 18 Dec 2000 03:42:10 -0500 (EST)
> From: Daniel Berlin <dberlin@redhat.com>
>
> 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.
Thanks for the explanations. I have one question, though: If
AUTO_DEMANGLING can detect the mangling style, why was it not used
previously? Why did the previous version trust the fact that it was
looking at a GCC-compiled program more than it trusted auto-detection?
> > > I recall that I had to make a change in GDB at the time to make it
> > recognize DJGPP programs as compiled by GCC. I'd like to make sure
> > this change doesn't undo what I did back then. (Unfortunately, I
> > don't have a recent snapshot on my machine and don't have time to
> > download and try it, to find this out myself.)
>
> No, it doesn't, unless your change was broken to begin with (IE depended
> on the old-abi mangling being present, which won't work now anyway).
The change had to do with how GCC-compiled programs was recognized.
The original code didn't get it right, in the DJGPP case. I forget
the details, but can dust them off, if that's important.