From: Michael Elizabeth Chastain <mec@shout.net>
To: fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix logic error suppressing attach.exp tests
Date: Thu, 28 Feb 2002 17:48:00 -0000 [thread overview]
Message-ID: <200203010148.g211mas19189@duracef.shout.net> (raw)
I proofread this and it looks good to me, with one gotcha: you need to
add "2002" to the copyright dates.
I tested this on:
target=native
host=i686-pc-linux-gnu%rh-7.2
gdb=HEAD%20020226
gcc=2.95.3, 3.0.4, gcc-3_1-branch%20020226, HEAD%20020226
glibc=vendor
goption=-gdwarf-2, -gstabs+
The results are flawless: all PASS on all configurations.
I don't have approval authority in testsuite/gdb.base but I like this patch.
Can anyone test it on more targets and hosts?
Michael C
===
2002-02-28 Fred Fish <fnf@redhat.com>
* gdb.base/attach.exp: Fix logic error that was suppressing this
test for all non hppa*-*-hpux* targets, instead of the hp target.
Move comments closer to the suppression point.
next reply other threads:[~2002-03-01 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 17:48 Michael Elizabeth Chastain [this message]
2002-03-25 11:48 ` Fred Fish
2002-03-25 11:56 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 13:15 Fred Fish
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=200203010148.g211mas19189@duracef.shout.net \
--to=mec@shout.net \
--cc=fnf@redhat.com \
--cc=gdb-patches@sources.redhat.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