From: Stan Shebs <stan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: why do we set prms_id/bug_id in GDB testcases?
Date: Mon, 26 Apr 2010 19:09:00 -0000 [thread overview]
Message-ID: <4BD5E4D2.6020702@codesourcery.com> (raw)
In-Reply-To: <20100426170109.GE2732@adacore.com>
Joel Brobecker wrote:
> Hello,
>
> It's a question that has been nagging at me problably since I decided
> that I was going to understand how to write testing with only stuff
> that is actually useful, and following the recommended style...
>
> We often start testcases with the following statements:
>
> set prms_id 0
> set bug_id 0
>
> [...]
>
> Maybe it's used internally by dejagnu? (I couldn't find evidence of that
> in the dejagnu manual)
>
>
It might have been used by some semi-internal Cygnus reporting thing, or
just as likely it was intended to be part of the one of the many
unimplemented ideas in Dejagnu. I would just whack it from GDB testsuite.
In fact I would go further, and say that *anything* in the GDB testsuite
without a known use should be deleted. The unfinished bits routinely
soak up our time puzzling over what they are supposed to be for. If
someone has a use for some bit, then it's up to them to document in the
testsuite somewhere.
Stan
next prev parent reply other threads:[~2010-04-26 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 17:01 Joel Brobecker
2010-04-26 19:00 ` Tom Tromey
2010-04-26 19:09 ` Stan Shebs [this message]
2010-04-26 22:11 ` Joel Brobecker
2010-05-05 18:14 ` Joel Brobecker
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=4BD5E4D2.6020702@codesourcery.com \
--to=stan@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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