From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: duplicate test message style?
Date: Wed, 07 Jul 2004 21:41:00 -0000 [thread overview]
Message-ID: <40EC6DF9.1000300@gnu.org> (raw)
Michael,
To stop those duplicate messages I add a suffix to each test, although
not consistently. I've used various separators - ",", ";", "for" - vis:
PASS: gdb.base/sigbpt.exp: nopass SIGSEGV; stepi bp before segv
PASS: gdb.base/sigbpt.exp: nopass SIGSEGV, stepi bp before segv
PASS: gdb.base/sigbpt.exp: nopass SIGSEGV for stepi bp before segv
I should do this consistently. How do either of:
PASS: gdb.base/sigbpt.exp: nopass SIGSEGV; stepi bp before segv
PASS: gdb.base/sigbpt.exp: set breakpoint 0 of 1; stepi bp before segv
PASS: gdb.base/sigbpt.exp: stepi out of handler; stepi bp before segv
PASS: gdb.base/sigbpt.exp: clear breakpoint 0 of 1; stepi bp before segv
or:
PASS: gdb.base/sigbpt.exp: stepi bp before segv; nopass SIGSEGV
PASS: gdb.base/sigbpt.exp: stepi bp before segv; set breakpoint 0 of 1
PASS: gdb.base/sigbpt.exp: stepi bp before segv; stepi out of handler
PASS: gdb.base/sigbpt.exp: stepi bp before segv; clear breakpoint 0 of 1
grab you? That is a ``;'' separator with the common text either first
or second.
Andrew
next reply other threads:[~2004-07-07 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 21:41 Andrew Cagney [this message]
2004-07-08 3:23 Michael Elizabeth Chastain
2004-07-08 6:18 ` Joel Brobecker
2004-07-08 14:22 ` 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=40EC6DF9.1000300@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@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