From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: carlton@kealia.com, gdb@sources.redhat.com, ian@wasabisystems.com
Subject: Re: C++/Java regressions
Date: Tue, 25 Nov 2003 15:06:00 -0000 [thread overview]
Message-ID: <20031125150615.GA379@nevyn.them.org> (raw)
In-Reply-To: <20031125144950.9E1EC4B40A@berman.michael-chastain.com>
On Tue, Nov 25, 2003 at 09:49:50AM -0500, Michael Chastain wrote:
> Good morning,
>
> I see the same regressions that David does. This happened in all
> my gcc-3 configurations. If you want a specific configuration:
>
> target = native, host = i686-pc-linux-gnu, osversion = red-hat-8.0
> gdb = HEAD 2003-11-25 04:21:57 UTC
> gcc = 3.3.2
> binutils = 2.14
> glibc = 2.2.93-5-rh
> gformat = dwarf-2
> glevel = 2
>
> I have two issues.
>
> === Issue #1: the demangler changed its interface.
>
> The demangler used to return parameters all the time, but now it looks
> like it returns parameters only if DMGL_PARAMS is given.
>
> This change did not happen with "complete rewrite". It happened
> with the followup patch:
>
> 2003-11-22 Ian Lance Taylor <ian@wasabisystems.com>
>
> * cp-demangle.c (d_encoding): Add top_level parameter. Change all
> callers.
> (print_usage): Display new -p option.
> (long_options): Add --no-params.
> (main): Accept and handle -p.
>
> So the questions are:
>
> (A) Does gdb want to keep getting the parameters?
> (My answer: yes we do).
>
> (B) If we want the parameters, should we change gdb to set DMGL_PARAMS,
> or should we ask the demangler to keep giving us the parameters with
> our existing flags, which is usually just DMGL_ANSI? (My answer:
> let Ian tell us what the interface actually is, and then we'll adapt
> gdb to match).
The former, since ths has been the documented interface to the
demangler forever. I believe the GNU v2 demangler supported it. But I
thought we did everywhere - where aren't we that this caused a problem?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-11-25 15:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 14:49 Michael Elizabeth Chastain
2003-11-25 15:06 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 22:48 Michael Elizabeth Chastain
2003-11-26 21:44 Michael Elizabeth Chastain
2003-11-26 22:21 ` Ian Lance Taylor
2003-11-26 22:28 ` Daniel Jacobowitz
2003-11-26 22:34 ` Ian Lance Taylor
2003-11-26 21:18 Michael Elizabeth Chastain
2003-11-26 21:33 ` Ian Lance Taylor
2003-11-25 17:06 Michael Elizabeth Chastain
2003-11-25 17:14 ` David Carlton
2003-11-25 17:59 ` Daniel Jacobowitz
2003-11-25 15:33 Michael Elizabeth Chastain
2003-11-25 4:44 Michael Elizabeth Chastain
2003-11-25 17:54 ` Ian Lance Taylor
2003-11-25 1:37 David Carlton
2003-11-25 3:58 ` Ian Lance Taylor
2003-11-26 4:04 ` Ian Lance Taylor
2003-11-26 15:32 ` Daniel Jacobowitz
2003-11-26 21:05 ` Ian Lance Taylor
2003-11-26 21:11 ` David Carlton
2003-11-26 21:12 ` Daniel Jacobowitz
2003-11-26 21:32 ` Ian Lance Taylor
2003-12-01 16:45 ` Daniel Jacobowitz
2003-11-30 2:57 ` Jim Blandy
2003-11-30 3:12 ` Daniel Jacobowitz
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=20031125150615.GA379@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.com \
--cc=mec.gnu@mindspring.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