Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA]: testsuite/gdb.base/a2-bin.exp: Consider `needs_status_wrapper' target_info
Date: Wed, 05 Dec 2001 12:29:00 -0000	[thread overview]
Message-ID: <20011205152834.A19151@nevyn.them.org> (raw)
In-Reply-To: <20011205211708.I29719@cygbert.vinschen.de>

On Wed, Dec 05, 2001 at 09:17:08PM +0100, Corinna Vinschen wrote:
> On Wed, Dec 05, 2001 at 02:54:40PM -0500, Daniel Jacobowitz wrote:
> > On Wed, Dec 05, 2001 at 08:25:07PM +0100, Corinna Vinschen wrote:
> > > 2001-12-05  Corinna Vinschen  <vinschen@redhat.com>
> > > 
> > > 	* gdb.base/a2-bin.exp: Pass first test even if the return
> > > 	code is 0 if target_info `needs_status_wrapper' exists.
> > 
> > Please don't turn this into a PASS; it didn't really test anything as I
> > read it.  "unsupported" is probably the appropriate return code.
> 
> I don't think so.  The test tests that the application returns
> it's usage so it has tested that the application got it's argc
> correctly.  That's what the test is for, right?  It's just an
> _additional_ test that the return code is 1.  It's not GDB's
> fault that the target can't return the return code correctly.

[BTW, it's a2-run.exp]

OK, I misread.  You might want to break this up into two tests;
you can just replace the one pass by two passes, and the pass you were
adding by a pass and an unsupported.  May not be worth the effort.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-12-05 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 11:25 Corinna Vinschen
2001-12-05 11:55 ` Daniel Jacobowitz
2001-12-05 12:17   ` Corinna Vinschen
2001-12-05 12:29     ` Daniel Jacobowitz [this message]
2002-01-21  8:12     ` Fernando Nasser
2002-01-20 16:08 ` Andrew Cagney

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=20011205152834.A19151@nevyn.them.org \
    --to=drow@mvista.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