Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: gdb@sources.redhat.com
Subject: Re: duplicate test message style?
Date: Thu, 08 Jul 2004 03:23:00 -0000	[thread overview]
Message-ID: <20040708032333.555FE4B104@berman.michael-chastain.com> (raw)

ac> PASS: gdb.base/sigbpt.exp: nopass SIGSEGV; stepi bp before segv
ac> PASS: gdb.base/sigbpt.exp: nopass SIGSEGV, stepi bp before segv
ac> PASS: gdb.base/sigbpt.exp: nopass SIGSEGV for stepi bp before segv

This rubs me the wrong way because it's a distinction that humans
would not make.

ac> PASS: gdb.base/sigbpt.exp: nopass SIGSEGV; stepi bp before segv
ac> PASS: gdb.base/sigbpt.exp: set breakpoint 0 of 1; stepi bp before segv
ac> PASS: gdb.base/sigbpt.exp: stepi out of handler; stepi bp before segv
ac> PASS: gdb.base/sigbpt.exp: clear breakpoint 0 of 1; stepi bp before segv

This is okay.

ac> PASS: gdb.base/sigbpt.exp: stepi bp before segv; nopass SIGSEGV
ac> PASS: gdb.base/sigbpt.exp: stepi bp before segv; set breakpoint 0 of 1
ac> PASS: gdb.base/sigbpt.exp: stepi bp before segv; stepi out of handler
ac> PASS: gdb.base/sigbpt.exp: stepi bp before segv; clear breakpoint 0 of 1

This is also okay.

So if you have a preference, between the two, pick the one you want.

I have a slight preference for the second form.  Here's why.  If I ever
notice the message, it's usually a context where I need to dig in and
and analyze it.  I think it would be a little easier for me to search
off the "outer; inner" style rather than the "inner; outer style".
But both of them are pretty searchable so either is okay.

Michael C


             reply	other threads:[~2004-07-08  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08  3:23 Michael Elizabeth Chastain [this message]
2004-07-08  6:18 ` Joel Brobecker
2004-07-08 14:22   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-07-07 21:41 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=20040708032333.555FE4B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@gnu.org \
    --cc=gdb@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