From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org, cagney@gnu.org
Cc: kettenis@chello.nl, gdb-patches@sources.redhat.com
Subject: Re: [testsuite] Kfail signals.exp failures
Date: Mon, 09 Aug 2004 16:44:00 -0000 [thread overview]
Message-ID: <4117A9EC.nail4LF31OFF4@mindspring.com> (raw)
In-Reply-To: <41178316.7000906@gnu.org>
Andrew Cagney <cagney@gnu.org> wrote:
> You appear to have found a new bug. Given all the potential
> combinations of step / next / continue VS breakpoint at/in handler VS
> handle its self, we may want to split this out of signals.exp and into a
> new expanded test file. Either way, a new test is needed.
>
> BTW, does sigbpt.exp pass? It's testing a related stepi edge case.
>
> Michael, those KFAILs are not correct.
Mmmm, I seem to have put my foot in it. I will admit that I am beyond
my depth in dealing with the signals tests.
Perhaps we should move all the signals tests to a new subdirectory
gdb.signal, and delegate someone else to be senior maintainer for
that subdirectory? I would feel competent to be junior maintainer.
If we don't do that, then I'm going to try something new in gdb
maintainership: delegation. I'll ask for 2 or 3 expert volunteers,
and I'll approve a signals patch just when there's unanimous consent
among the experts.
And I've made a note to read up on signals tests.
Michael C
next prev parent reply other threads:[~2004-08-09 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 23:18 Daniel Jacobowitz
2004-08-09 7:00 ` Michael Chastain
2004-08-09 13:18 ` Daniel Jacobowitz
2004-08-09 7:46 ` Mark Kettenis
2004-08-09 13:11 ` Daniel Jacobowitz
2004-08-09 13:58 ` Andrew Cagney
2004-08-09 15:18 ` Daniel Jacobowitz
2004-08-09 16:17 ` Andrew Cagney
2004-08-09 16:44 ` Michael Chastain [this message]
2004-08-24 22:35 ` Andrew Cagney
2004-08-27 18:42 ` Mark Kettenis
2004-08-09 19:43 ` Andreas Schwab
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=4117A9EC.nail4LF31OFF4@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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