From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Cc: Andrew Cagney <ac131313@redhat.com>
Subject: Re: gdb.cp/annota3.exp: annotate-quit
Date: Fri, 26 Sep 2003 00:01:00 -0000 [thread overview]
Message-ID: <yf2llsc8ljz.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20030925235300.GA22524@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 25 Sep 2003 19:53:00 -0400")
On Thu, 25 Sep 2003 19:53:00 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> On Thu, Sep 25, 2003 at 04:41:50PM -0700, David Carlton wrote:
>> I noticed that, in the transition from gdb.cp/annota2.exp to
>> gdb.cp/annota3.exp, the KFAIL for annotate-quit got removed; am I
>> correct in assuming that this is just an oversight? It still
>> consistently fails for me (i686-pc-linux-gnu, GCC 3.1, DWARF 2).
> It doesn't fail here. I'd really really like to find out what the
> difference is.
Interesting. I assume the corresponding test in annota2.exp passes
for you as well?
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-09-26 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 23:41 David Carlton
2003-09-25 23:53 ` Daniel Jacobowitz
2003-09-26 0:01 ` David Carlton [this message]
2003-09-26 14:00 ` Daniel Jacobowitz
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=yf2llsc8ljz.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@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