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

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

It's a copy of a previous gdb.sum (the one I got from running
the testsuite before making my change). I am realizing that my
situation might be different from yours, since in my case, the
compiler can change daily. I also work on dozens of different
machines, many different OSes, arches, etc. What I mean that by
is that everything changes all the time. But perhaps in your
case, keeping a reference gdb.sum around might be a good option
for you and save you the trouble of having to generate it every
time. There is still the fact that the testsuite also evolves
quite a bit, so even in your case this might not be a practical
suggestion.

-- 
Joel


  reply	other threads:[~2007-01-13 14:00 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
2007-01-13 14:00     ` Joel Brobecker [this message]
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=20070113140054.GK20110@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --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