From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com,
Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: RFC: gdb.c++/main-falloff.exp (a new KFAIL)
Date: Fri, 03 Jan 2003 20:53:00 -0000 [thread overview]
Message-ID: <ro17kdmlzv7.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20021230154641.GA23984@nevyn.them.org>
On Mon, 30 Dec 2002 10:46:41 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> Secondly, I really dislike this form. Adding gdb_expect's all over is
> bad, because gdb_test has a much more thorough list of things to expect
> indicating various errors. Better would be to solve this problem with
> a little TCL. What do you think of:
> gdb_test_multiple "info locals" \
> {pass "(i|j|k) = (101|102|103)\r\n(i|j|k) = (101|102|103)\r\n(i|j|k) = (101|102|103)"
> kfail "gdb/900" "No locals."} \
> "testing locals"
Something like this seems reasonable to me. It would be nice if the
branches could execute arbitrary code, like gdb_expect does, though,
so that the xfails/kfails could be conditional on the operating
system, debug format, or whatever. Though I do like the fact that
your version means that you only have to type the message once for all
branches (and presumably the message would be optional if the message
is the same as the command).
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-01-03 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 2:36 Michael Elizabeth Chastain
2002-12-30 8:05 ` Daniel Jacobowitz
2003-01-03 20:53 ` David Carlton [this message]
2002-12-30 8:09 Michael Elizabeth Chastain
2002-12-30 11:41 ` Daniel Jacobowitz
2003-01-03 21:17 Michael Elizabeth Chastain
2003-01-03 21:24 ` David Carlton
2003-01-03 21:37 ` Daniel Jacobowitz
2003-01-03 21:45 Michael Elizabeth Chastain
2003-01-03 21:49 ` Daniel Jacobowitz
2003-01-03 22:03 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=ro17kdmlzv7.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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