Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: Daniel Berlin <dberlin@redhat.com>
Cc: Michael Elizabeth Chastain <chastain@cygnus.com>,
	fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] testsuite/gdb.c++/ref-types.exp: use runto
Date: Fri, 16 Mar 2001 14:29:00 -0000	[thread overview]
Message-ID: <3AB29121.7F3BC7BB@cygnus.com> (raw)
In-Reply-To: <m2snkd77l0.fsf@dynamic-addr-83-177.resnet.rochester.edu>

Daniel Berlin wrote:
> 
> Michael Elizabeth Chastain <chastain@cygnus.com> writes:
> 
> > Fernando Nasser writes:
> > > But I wonder if we should not call gdb_start_again() the first time
> > > around instead of having the code duplicated.  It is exactly the same
> > > thing.
> >
> > Doh!  I'm so busy with individual lines, I missed an opportunity to
> > take out a whole section.
> >
> > ref_types.exp works now, so I am going to leave it alone and fix more
> > pressing problems first: like gdb.c++/userdef.exp, which has no code,
> > and gdb.c++/virtfunc.exp, which XFAILs some tests because gdb
> > doesn't   [do the right thing]
> ^^^^^^^
> can't
> Not doesn't.
> Can't.
> 
> They need to be xfail'd for old-abi, but not for new-abi.

In that case, (and without having looked at the test), 
I wonder if it would be possible to do something like the following?

  send_gdb "whatever\n
"
  gdb_expect {
    -re "new_abi_pattern" {
	pass "this test";
    }
    -re "old_abi_pattern" {
	setup_xfail "this test";
	fail "this test"
    }
    default {
	fail "this test";
    }
  }


  reply	other threads:[~2001-03-16 14:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200103161807.KAA06081@bosch.cygnus.com>
2001-03-16 12:00 ` Fernando Nasser
2001-03-16 13:00 ` Daniel Berlin
2001-03-16 14:29   ` Michael Snyder [this message]
2001-03-17 14:37 Michael Elizabeth Chastain
  -- strict thread matches above, loose matches on Subject: below --
2001-03-17 12:42 Michael Elizabeth Chastain
2001-03-17 15:31 ` Daniel Berlin
2001-03-17 12:35 Michael Elizabeth Chastain
2001-03-17 14:23 ` Daniel Berlin
2001-03-16 21:00 Michael Elizabeth Chastain
2001-03-17 11:12 ` Daniel Berlin
2001-03-16 16:03 Michael Elizabeth Chastain
2001-03-16 14:50 Michael Elizabeth Chastain
2001-03-16 14:55 ` Daniel Berlin
2001-03-16 14:49 Michael Elizabeth Chastain
2001-03-16 14:55 ` Daniel Berlin
     [not found] ` <20010316215907.A3607@redhat.com>
2001-03-17 11:59   ` Daniel Berlin
2001-03-16 14:35 Michael Elizabeth Chastain
2001-03-16 14:40 ` Fernando Nasser
2001-03-16 14:43 ` Daniel Berlin
2001-03-16 14:44 ` Daniel Berlin
2001-03-16 13:15 Michael Elizabeth Chastain
2001-03-16 13:21 ` Fernando Nasser
2001-03-16 15:14   ` Peter.Schauer
2001-03-16 15:17     ` Daniel Berlin
2001-03-16 15:45       ` Michael Snyder
2001-03-16 15:49         ` Daniel Berlin
2001-03-16 15:19   ` Andrew Cagney
2001-03-16 15:21     ` Daniel Berlin
2001-03-17  7:56   ` Daniel Berlin
2001-03-04 15:25 Michael Elizabeth Chastain
2001-02-24  0:16 Michael Elizabeth Chastain

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=3AB29121.7F3BC7BB@cygnus.com \
    --to=msnyder@cygnus.com \
    --cc=chastain@cygnus.com \
    --cc=dberlin@redhat.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.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