Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] New constvars.exp tests
Date: Thu, 10 Oct 2002 13:39:00 -0000	[thread overview]
Message-ID: <20021010203953.GA26607@nevyn.them.org> (raw)
In-Reply-To: <1021010203259.ZM16308@localhost.localdomain>

On Thu, Oct 10, 2002 at 01:32:59PM -0700, Kevin Buettner wrote:
> I am about to submit a patch which causes ptype to print a struct with
> qualifiers correctly.  E.g, for the "crass" test, gdb currently
> exhibits the following behavior:
> 
>     (gdb) ptype crass
>     type = struct crass {
> 	char * constptr;
>     }
> 
> This is incorrect because gdb failed to print a space in between
> "const" and "ptr".
> 
> Unfortunately, if you don't use Dwarf 2, you'll simply end up seeing
> 
>     type = struct crass {
> 	char *ptr;
>     }
> 
> ...which is also wrong, but not unexpected (hence the xfail).

Not necessarily.  Recent versions of GCC will emit const qualifiers in
stabs, leading to a horde of XPASS's in our testsuite... but that's a
problem for another patch.

Nice to see someone working on the type printer.  I'm planning to
submit a "hit it over the head with a board" patch in a couple of days,
to let us simulate the output of the various demangling styles.

> 	* gdb.base/constvars.c (struct crass, struct crisp): New structs.
> 	* gdb.base/constvars.exp (ptype crass, ptype crisp): New tests.

FWIW, these test cases look correct to me.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-10-10 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 13:33 Kevin Buettner
2002-10-10 13:39 ` Daniel Jacobowitz [this message]
2002-10-17 13:08 ` Fernando Nasser
2002-10-17 13:31   ` Kevin Buettner
2002-10-17 17:11     ` Kevin Buettner
2002-10-17 13:25 ` Kevin Buettner

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=20021010203953.GA26607@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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