Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Jason Merrill <jason@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
	gdb@sources.redhat.com, fnf@redhat.com
Subject: Re: gdb.c++ failures
Date: Thu, 10 Jan 2002 11:32:00 -0000	[thread overview]
Message-ID: <20020110143328.B9479@nevyn.them.org> (raw)
In-Reply-To: <wvl1ygyf1w1.fsf@prospero.cambridge.redhat.com>

On Thu, Jan 10, 2002 at 07:21:18PM +0000, Jason Merrill wrote:
> >>>>> "Michael" == Michael Elizabeth Chastain <mec@shout.net> writes:
> 
> > Jason Merrill writes:
> >> method.exp: The 'print this' tests are failing because gdb is printing
> >> the types as, say, (A * const), and the test just wants (A *).  The
> >> former is correct, since 'this' is readonly.  Any objection to changing
> >> the test (and others affected) to allow the const?
> 
> > Fred Fish submitted a patch for this.
> 
> Quite so.  Fred, it looks good to me.

I agree.

> > There is a second issue in the patch about the type of "this" in const
> > methods.  The type should be "const A *", and I would be willing to
> > accept "const A * const".  But gdb with stabs is printing just plain "A
> > *".
> 
> The stabs output from gcc ignores const and volatile.  There is even a
> comment saying that "stabs does not distinguish const and volatile".
> The method qualifiers are described, and gdb could do the work to apply
> them to the type of 'this', but it's probably fine just to leave it as it
> is.

There are documented extensions to STABS to express both const and
volatile.  GDB supports them, and documents them - see info stabs. 
They're originally Sun extensions.

Could I persuade you to add them to GCC?  It would take you less time
than I.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-01-10 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  9:12 Michael Elizabeth Chastain
2002-01-10 11:21 ` Jason Merrill
2002-01-10 11:32   ` Daniel Jacobowitz [this message]
2002-01-10 13:25     ` Jason Merrill
2002-01-11 17:11       ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2002-01-10  5:18 Jason Merrill
2002-01-10 11:52 ` Daniel Jacobowitz
2002-01-10 12:59   ` Jason Merrill

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=20020110143328.B9479@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=fnf@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jason@redhat.com \
    --cc=mec@shout.net \
    /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