Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: tests for MI commands
Date: Wed, 27 Jul 2005 12:50:00 -0000	[thread overview]
Message-ID: <20050727125049.GB16612@white> (raw)
In-Reply-To: <17127.29797.456624.592127@farnswood.snap.net.nz>

>  > +FAIL: gdb.mi/mi2-var-display.exp: get children local variable weird
>  >
>  > Please fix them - I think the easiest thing to do is to revert the
>  > changes to the affected source files and switch those two modified
>  > tests to using new source files.
> 
> Given the scarce resources for this unpaid work I ask you again to consider
> removing the mi2-*.exp files and just test the current version of MI.  The
> reality is that they serve no useful purpose (mi-*.exp tests would still
> pass if GDB was invoked with "-i=mi2") and they require effort that could
> be better spent on other things.

Nick, I don't fully agree that the mi2- tests serve no useful purpose.
The mi2- tests make sure that the MI2 protocol is completly tested (MI2 
works no less then what the mi2- tests say they do), and the mi- tests 
make sure that the current development MI protocol is being tested. I 
think it's important to keep both tests for this reason. Do you still
think they should be removed after this explanation?

For instance, it's possible that a command works differently between the
2 versions (don't know if this currently even happens).

Thanks,
Bob Rossi


  reply	other threads:[~2005-07-27 12:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20  4:51 Nick Roberts
2005-07-24 21:19 ` Daniel Jacobowitz
2005-07-26 23:31   ` Nick Roberts
2005-07-27  0:27     ` Daniel Jacobowitz
2005-07-27  3:04       ` Nick Roberts
2005-07-27  3:55         ` Daniel Jacobowitz
2005-07-27 11:46           ` Nick Roberts
2005-07-27 12:50             ` Bob Rossi [this message]
2005-07-27 20:52               ` Nick Roberts
2005-07-27 21:49                 ` Daniel Jacobowitz
2005-07-27 22:09                   ` Nick Roberts
2005-07-27 21:03             ` Mark Kettenis
2005-07-27 22:23               ` Nick Roberts
2005-07-28  0:08                 ` Paul Gilliam
2005-07-28  0:18                 ` Stan Shebs
2005-07-28  0:21                 ` Daniel Jacobowitz
2005-07-28  1:39                   ` Nick Roberts
2005-07-31 22:11                     ` Daniel Jacobowitz
2005-07-31 23:32                       ` Nick Roberts
2005-08-01  1:55                         ` Daniel Jacobowitz
2005-07-27 21:25             ` Mark Kettenis
2005-07-29  7:32           ` Nick Roberts
2005-07-31 21:25             ` Daniel Jacobowitz
2005-07-31 23:32               ` Nick Roberts
2005-08-01  1:57                 ` Daniel Jacobowitz

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=20050727125049.GB16612@white \
    --to=bob@brasko.net \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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