Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: kettenis@chello.nl, gdb@sources.redhat.com
Subject: Re: C++ testsuite changes
Date: Thu, 01 Jan 2004 21:08:00 -0000	[thread overview]
Message-ID: <20040101210843.GA11982@nevyn.them.org> (raw)
In-Reply-To: <20040101200526.0916B4B35A@berman.michael-chastain.com>

On Thu, Jan 01, 2004 at 03:05:26PM -0500, Michael Chastain wrote:
> Hi Mark,
> 
> > I noticed some PASSes that previously were XFAILs.  Is that correct?
> 
> Let me have a look .... yes, these are the ptype's that I fixed.
> 
> In particular, I changed the results for tests like this:
> 
>   ptype class vC
>   type = class vC : public virtual vA {
>     private:
>       vA *_vb.2vA;
>     public:
>       int vc;
>       int vx;
>   }
> 
> The old test would XFAIL this because gdb prints the virtual base
> pointer, _vb.2vA.  I don't consider that a bug so I don't XFAIL it
> any more.

Eh... why don't you?  It's a feature that we don't print the virtual
base pointer in recent gcc/dwarf combinations.  It could be implemented
for stabs or older gccs or whichever it is that used to xfail, but no
one has taken the time yet.

I would really prefer it if you didn't rewrite the tests to accomodate
the ABI change (a very specific change) and change all sorts of other
tests at the same time.  It makes it impossible to tell from your
patches when you make a change like this one.

> > I get some wierd ERRORs in virtfunc.exp.
> > As far as I can tell, GDB doesn't crash.
> 
> This is stumping me.
> 
> I proofread "ptype D" forwards and backwards and compared it to
> the code before and the code after, and I don't see any mistakes.
> 
> What is your host triple?
> Which versions of TCL, Expect, and Dejagnu are you using?
> Can you mail me the whole gdb.log section for virtfunc.exp?
> 
> Michael C
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-01-01 21:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01 20:05 Michael Elizabeth Chastain
2004-01-01 21:08 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-01 23:07 Michael Elizabeth Chastain
2004-01-01 22:41 Michael Elizabeth Chastain
2004-01-01 23:02 ` Mark Kettenis
2004-01-01 22:16 Michael Elizabeth Chastain
2004-01-01 22:19 ` Daniel Jacobowitz
2004-01-01 21:41 Michael Elizabeth Chastain
2004-01-01 21:47 ` Daniel Jacobowitz
2004-01-01 21:23 Michael Elizabeth Chastain
2004-01-01 21:35 ` Daniel Jacobowitz
2004-01-01 14:26 Mark Kettenis

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=20040101210843.GA11982@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --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