From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [obish] Convert attach.exp to gdb_test_multiple
Date: Mon, 12 Jul 2004 14:30:00 -0000 [thread overview]
Message-ID: <40F2A092.90803@gnu.org> (raw)
In-Reply-To: <20040709002351.03A074B104@berman.michael-chastain.com>
>>I'll leave committing this to tomorrow (i.e., after the branch date).
>>> Still passes on amd64 GNU/Linux and PPC NetBSD.
>
>
> Hey, we don't have any ppc netbsd results in gdb-testers@.
Nor amd64 GNU/Linux, ppc64 GNU/Linux, ... :-)
> Can I get you to send an abridged gdb.sum file to gdb-testers?
>
> grep -v '^PASS:' gdb.sum
> add a couple lines at the top:
> netbsd/ppc
> kernel version number
> compiler name and version number
> mail to gdb-testers@
Should there be a gdb/gdb_XXX.sh script that does this, or the
generation of the file made part of make check?
Andrew
next prev parent reply other threads:[~2004-07-12 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 0:23 Michael Elizabeth Chastain
2004-07-12 14:30 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-12 18:25 Michael Elizabeth Chastain
2004-07-08 21:09 Andrew Cagney
2004-07-12 14:26 ` Andrew Cagney
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=40F2A092.90803@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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