Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: carlton@math.stanford.edu, gdb-patches@sources.redhat.com
Subject: Re: RFC: gdb.c++/main-falloff.exp (a new KFAIL)
Date: Fri, 03 Jan 2003 21:49:00 -0000	[thread overview]
Message-ID: <20030103214946.GA9980@nevyn.them.org> (raw)
In-Reply-To: <200301032145.h03Lj3Q19841@duracef.shout.net>

On Fri, Jan 03, 2003 at 03:45:03PM -0600, Michael Elizabeth Chastain wrote:
> As David C mentioned, gdb_test_multiple cannot replace send_gdb/gdb_expect,
> because there is no room in the syntax to add TCL code blocks
> which some tests use to check compiler version, target version.

That's why we don't have a fixed syntax yet.  I have some better ideas.

> > If it's bugging you that bad I'll do it or something similar tomorrow
> > morning.
> 
> That would be great.
> 
> But: is it okay with you if we de-couple these things and proceed
> with the KFAIL bacchanal?
> 
> Michael C
> pushy new yorker

No, please wait until tomorrow so that I can give you something less
error prone.

Daniel J
pushy pittsburgher


  reply	other threads:[~2003-01-03 21:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 21:45 Michael Elizabeth Chastain
2003-01-03 21:49 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-03 22:03 Michael Elizabeth Chastain
2003-01-03 21:17 Michael Elizabeth Chastain
2003-01-03 21:24 ` David Carlton
2003-01-03 21:37 ` Daniel Jacobowitz
2002-12-30  8:09 Michael Elizabeth Chastain
2002-12-30 11:41 ` Daniel Jacobowitz
2002-12-30  2:36 Michael Elizabeth Chastain
2002-12-30  8:05 ` Daniel Jacobowitz
2003-01-03 20:53   ` David Carlton

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=20030103214946.GA9980@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --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