Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
		Hui Zhu <teawater@gmail.com>
Subject: Re: [RFA] New testes for process record save/restore commands
Date: Mon, 19 Oct 2009 20:03:00 -0000	[thread overview]
Message-ID: <20091019200322.GD5282@adacore.com> (raw)
In-Reply-To: <4ADCC1CE.1090304@vmware.com>

> 2009-10-19  Michael Snyder  <msnyder@vmware.com>
> 
> 	* gdb.reverse/break-precsave.exp: New test.
> 	* gdb.reverse/consecutive-precsave.exp: Ditto.
> 	* gdb.reverse/finish-precsave.exp: Ditto.
> 	* gdb.reverse/i386-precsave.exp: Ditto.
> 	* gdb.reverse/machinestate-precsave.exp: Ditto.
> 	* gdb.reverse/sigall-precsave.exp: Ditto.
> 	* gdb.reverse/solilb-precsave.exp: Ditto.
> 	* gdb.reverse/step-precsave.exp: Ditto.
> 	* gdb.reverse/until-precsave.exp: Ditto.
> 	* gdb.reverse/watch-precsave.exp: Ditto.

I only quickly scanned the files, since they are essentially duplicates
of already-existing testcases. I didn't expect to find anything, but
I actually did notice a couple of things:

  - Use of send_gdb/gdb_expect which should be replaced by gdb_test_multiple
    (too bad we didn't catch those in the current ones when the testcases
    were checked in)
  - unnecessary "return 0" at the end of the script.

I think we shouldn't put anything unnecessary in these files, as we tend
to forget why we put them, and the next developer who, like me, writes
testcase by copy/paste, will repeat the pattern because he's afraid of
breaking something otherwise.

-- 
Joel


  reply	other threads:[~2009-10-19 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 19:51 Michael Snyder
2009-10-19 20:03 ` Joel Brobecker [this message]
2009-10-20  5:23   ` Joel Brobecker
2009-10-22 19:59   ` Michael Snyder
2009-10-23  6:56     ` Hui Zhu
2009-10-23 14:07       ` Paul Pluzhnikov
2009-10-26  8:51         ` Hui Zhu

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=20091019200322.GD5282@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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