From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com, kettenis@chello.nl
Subject: Re: C++ testsuite changes
Date: Thu, 01 Jan 2004 21:47:00 -0000 [thread overview]
Message-ID: <20040101214744.GC12798@nevyn.them.org> (raw)
In-Reply-To: <20040101214033.BD3764B35A@berman.michael-chastain.com>
On Thu, Jan 01, 2004 at 04:40:33PM -0500, Michael Chastain wrote:
> On reflection, actually, I should keep the output identical for a
> rewrite. And I still have a bunch of nice "before" files.
> So I'll change classes.exp, derivation.exp, overload.exp, and
> virtfunc.exp so that they print the same results in the same order.
>
> Then I can fix the problems in the test script one problem at a time.
>
> I can reproduce Mark's problem with virtfunc.exp by using the
> sourceware version of TCL+Expect+Dejagnu rather than the released
> versions. In particular, the sourceware version of Expect was last
> updated in 1998. Argh! So I'll find some way to write virtfunc.exp
> that works with these versions of TCL+Expect+Dejagnu.
Can you identify what expect feature was causing the problem? I'm
quite curious.
I suspect we need to do an expect update...
> As far the virtual base pointer goes, if you consider it a bug in gdb,
> then I'll write a KFAIL arm for it and KFAIL it.
Thank you.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-01 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 21:41 Michael Elizabeth Chastain
2004-01-01 21:47 ` 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:23 Michael Elizabeth Chastain
2004-01-01 21:35 ` Daniel Jacobowitz
2004-01-01 20:05 Michael Elizabeth Chastain
2004-01-01 21:08 ` 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=20040101214744.GC12798@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