From: Daniel Jacobowitz <drow@mvista.com>
To: gdb <gdb@sources.redhat.com>
Subject: Re: gdb.c++/annota2.exp: annotate-quit
Date: Thu, 06 Feb 2003 21:41:00 -0000 [thread overview]
Message-ID: <20030206214103.GA20993@nevyn.them.org> (raw)
In-Reply-To: <ro1hebhw3d0.fsf@jackfruit.Stanford.EDU>
On Thu, Feb 06, 2003 at 12:39:23PM -0800, David Carlton wrote:
> Sometime between yesterday and today, the test gdb.c++/annota2.exp,
> which had been consistently KFAILing for me, started consistently
> passing. Is anybody else seeing this? Does anybody currently see it
> KFAIL? Is there any chance that the interpreter patch from yesterday
> or today might have fixed this bug? (The bug has nothing to do with
> C++ or annotations: it's just that GDB wasn't always responding to a
> ^C as it should.)
I see this also; but it's done this in the past, so I'm reluctant to
claim that it's actually fixed.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-06 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 20:39 David Carlton
2003-02-06 21:41 ` Daniel Jacobowitz [this message]
2003-02-06 23:00 ` Mark Kettenis
2003-02-07 6:22 Michael Elizabeth Chastain
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=20030206214103.GA20993@nevyn.them.org \
--to=drow@mvista.com \
--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