This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Test suite docs
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb at sourceware dot org
- Date: Sat, 13 Jan 2007 15:53:50 +0200
- Subject: Re: Test suite docs
- References: <u8xg7i5oc.fsf@gnu.org> <20070113132846.GI20110@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 13 Jan 2007 17:28:46 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb@sourceware.org
>
> So, for lack of knowledge, I will not volunteer to write the doco up.
> However, here some of the things I do. Bear in mind that they might
> not be the most efficient way of doing things, but they should
> help you in the meantime.
Thanks.
> I use the latest official dejagnu release, along with one of the latest
> TCL and expect releases. They were the latest at the time when I did
> the install, which was a while ago (perhaps a couple of years).
I asked gnu.org sysadmins to install dejagnu, and they installed
version 1.4.4, which I think is the latest official release. So this
is okay in my case.
> > . How do I compare two runs? If diff'ing testsuite/gdb.sum is the
> > right way, it seems to not be documented anywhere, and gdb.sum
> > doesn't seem to be preserved across runs, so one must manually
> > copy it to avoid overwriting it. Am I missing something?
>
> I personnally use a home-made program that is essentially a smart
> diff tool for .sum files. It presents the information in 3 columns,
> showing only the differences. Column one, the result in the reference
> test; column 2, the result in the second .sum file; and column 3
> the label of the test.
>
> Here is an example of the output:
> % sumtool -c gdb.sum.ref gdb.sum
How do you produce gdb.sum.ref? is it by manually copying some
previous gdb.sum, or is there a better way?