From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, gdb@sources.redhat.com
Subject: Re: gdb.c++/annota2.exp: annotate-quit
Date: Fri, 07 Feb 2003 06:22:00 -0000 [thread overview]
Message-ID: <200302070622.h176Mln07953@duracef.shout.net> (raw)
dc> Is anybody else seeing this?
dc> Does anybody currently see it KFAIL?
I'll run it a couple of hundred times in the morning and report back.
dc> Is there any chance that the interpreter patch from yesterday
dc> or today might have fixed this bug?
Yes. The test case reads a prompt from gdb, sends a ^C to gdb,
and expects gdb to react to it. I suspect there's a race condition
involving job control so that the incoming ^C races with the
operating system enabling gdb to receive signals (as opposed to
the inferior receiving the signal). So something that touches
the main prompt/read loop could touch this.
(I admit I'm guessing a lot here).
Michael C
next reply other threads:[~2003-02-07 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 6:22 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 20:39 David Carlton
2003-02-06 21:41 ` Daniel Jacobowitz
2003-02-06 23:00 ` Mark Kettenis
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=200302070622.h176Mln07953@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--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