From: Michael Snyder <msnyder@vmware.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Pedro Alves <pedro@codesourcery.com>,
"teawater@gmail.com" <teawater@gmail.com>
Subject: Re: i386.record.floating.point.patch : with more testing and assurity
Date: Sun, 12 Jul 2009 11:12:00 -0000 [thread overview]
Message-ID: <4A591F54.3030207@vmware.com> (raw)
In-Reply-To: <736794.15455.qm@web112516.mail.gq1.yahoo.com>
paawan oza wrote:
> Hi,
> As I am submitting the patch for the first time, I am not much aware of gdb test suite.
> would you please guide me about how I can put the things in the testsuite ?
> is it the testsuite which comes along with the gdb source ?
> gdb\testsuite\gdb.base ??
> Regards,
> Oza.
Hi Oza,
Yes, we are talking about the automated regression testsuite that
comes with the gdb source tree, at src/gdb/testsuite. You'll need
to be familiar with it, both to use it and to write tests.
All tests for the GNU tools are written in (are you ready for this)
* dejagnu, which is a layer written on top of
* expect, which is a language written on top of
* tcl.
There are many many tests already in the testsuite. Each consists of
1) one 'expect' script, such as
src/gdb/testsuite/gdb.base/break-always.exp
2) one or more source files, such as
src/gdb/testsuite/gdb.base/break-always.c
I chose that one as a relatively simple example for you to look at.
Each script
* compiles the corresponding source file,
* starts gdb, and
* runs a set of gdb commands.
The output of the commands is automatically compared to a set
of expected outputs (hence the name 'expect'), and if the output
matches the expected output the script will output "PASS".
Otherwise it will output "FAIL".
We use these test scripts regularly, both to validate new patches,
and to make sure that new changes haven't broken any old changes.
To run the gdb tests, you need to have installed
* dejagnu version 1.4.4
* expect version 5.42.1
* tcl at least version 8.4
With those installed, you should be able to do the following
in your build tree, with these results: then we'll talk about
writing tests. ;-)
bash-3.00$ cd gdb/testsuite
bash-3.00$ make check RUNTESTFLAGS=break-always.exp
[some noise]
=== gdb tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /data/home/msnyder/cvs/localhost/oza/gdb/testsuite/config/unix.exp
as tool-and-target-specific interface file.
Running
/data/home/msnyder/cvs/localhost/oza/gdb/testsuite/gdb.base/break-always.exp
...
=== gdb Summary ===
# of expected passes 4
/data/home/msnyder/builds/native/oza/gdb/testsuite/../../gdb/gdb version
6.8.50.20090711-cvs -nw -nx
next prev parent reply other threads:[~2009-07-11 23:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 15:05 paawan oza
2009-07-01 5:53 ` Hui Zhu
2009-07-12 11:12 ` Michael Snyder [this message]
2009-07-12 17:47 ` paawan oza
2009-07-13 0:38 ` Michael Snyder
2009-07-13 17:03 ` Hui Zhu
2009-07-13 20:16 ` Michael Snyder
2009-07-15 9:21 ` Hui Zhu
2009-07-19 3:27 ` paawan oza
2009-07-18 23:36 ` paawan oza
[not found] <992589.56162.qm@web112513.mail.gq1.yahoo.com>
2009-07-26 19:10 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2009-07-26 14:27 paawan oza
2009-07-26 22:51 ` Michael Snyder
2009-07-27 1:09 ` Michael Snyder
2009-07-27 2:33 ` Samuel Bronson
2009-07-06 19:09 paawan oza
2009-07-06 19:05 paawan oza
2009-07-08 9:00 ` Hui Zhu
2009-07-12 9:52 ` Michael Snyder
2009-07-12 18:12 ` Michael Snyder
2009-07-06 19:03 paawan oza
2009-07-06 19:01 paawan oza
2009-07-04 5:19 paawan oza
2009-07-05 10:15 ` Hui Zhu
2009-07-03 18:55 paawan oza
2009-07-03 21:52 ` Michael Snyder
2009-07-02 7:40 paawan oza
2009-07-02 3:39 paawan oza
2009-07-02 3:34 paawan oza
2009-07-01 16:17 paawan oza
2009-07-05 18:33 ` Mark Kettenis
2009-07-01 16:02 paawan oza
2009-07-01 16:14 ` Mark Kettenis
2009-07-01 16:01 paawan oza
2009-07-01 15:59 paawan oza
2009-07-02 2:02 ` Hui Zhu
2009-06-30 13:23 paawan oza
2009-06-30 13:38 ` Pedro Alves
2009-06-30 13:42 ` Mark Kettenis
2009-06-04 14:50 paawan oza
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=4A591F54.3030207@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=paawan1982@yahoo.com \
--cc=pedro@codesourcery.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