Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Test suite docs
Date: Sat, 13 Jan 2007 13:54:00 -0000	[thread overview]
Message-ID: <u64bbhw29.fsf@gnu.org> (raw)
In-Reply-To: <20070113132846.GI20110@adacore.com> (message from Joel Brobecker 	on Sat, 13 Jan 2007 17:28:46 +0400)

> 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?


  reply	other threads:[~2007-01-13 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 10:26 Eli Zaretskii
2007-01-13 13:28 ` Joel Brobecker
2007-01-13 13:54   ` Eli Zaretskii [this message]
2007-01-13 14:00     ` Joel Brobecker
2007-02-24 15:51   ` Michael Snyder
2007-01-13 14:26 ` Mark Kettenis
2007-01-13 14:48   ` Eli Zaretskii
2007-01-13 15:05     ` Mark Kettenis
2007-01-13 15:16       ` Eli Zaretskii
2007-01-13 15:08   ` Eli Zaretskii
2007-01-13 15:29     ` Daniel Jacobowitz
2007-01-13 15:33     ` Mark Kettenis
2007-01-13 15:58       ` Daniel Jacobowitz
2007-01-13 18:01       ` Eli Zaretskii

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=u64bbhw29.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@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