Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Michael Snyder <msnyder@cygnus.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] Tweak for a gdb.mi test.
Date: Tue, 07 May 2002 20:06:00 -0000	[thread overview]
Message-ID: <3CD89631.4010201@cygnus.com> (raw)
In-Reply-To: <3CD88738.2E9B1BC4@redhat.com>

>>  From memory, a suggestion was to let people select the back-trace
>> policy independant of the current architecture.
> 
> 
> I thought we also had a policy of not inserting tests
> that we knew would fail on some targets?  Something about
> this being a regression test...

My understanding of the ``the regression test'' is that it stops people 
adding ``feature'' tests that demonstrate bugs in things that have never 
worked (or are not even implemented).  It avoids, among other things, 
the problem of not knowing of a FAIL is a bug in GDB or in a testcase 
that never worked.

I look at this test as something similar to call-ar-st.  It has been 
demonstrate to work on one platform (I think the original was Arm/eCos 
but more recently GNU/Linux i386) and should work on other platforms.

enjoy,
Andrew


  reply	other threads:[~2002-05-08  3:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 18:22 Michael Snyder
2002-05-07 18:30 ` Daniel Jacobowitz
2002-05-07 19:03   ` Michael Snyder
2002-05-07 19:42     ` Daniel Jacobowitz
2002-05-07 19:04   ` Andrew Cagney
2002-05-07 19:15     ` Michael Snyder
2002-05-07 20:06       ` Andrew Cagney [this message]
2002-05-08 13:50         ` Michael Snyder
2002-05-08 15:52           ` 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=3CD89631.4010201@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.com \
    --cc=msnyder@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