From: "Cary Coutant" <ccoutant@google.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc <gcc@gcc.gnu.org>, gdb@sourceware.org
Subject: Re: gdb test suite failure on i386 and x86_64 in gdb.base/break.exp
Date: Sat, 13 Sep 2008 17:00:00 -0000 [thread overview]
Message-ID: <c17be2b30809130959k71701590l5ebd8445e8ef75b5@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0809130147260.21852@digraph.polyomino.org.uk>
> This is PR 36690 which has various bits of analysis.
Thanks! I did search for this problem, but I guess I didn't use the
right terms, and it didn't turn up this bug report. Looks like if I
had done another search after analyzing the problem, it probably would
have turned up.
-cary
prev parent reply other threads:[~2008-09-13 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 1:28 Cary Coutant
2008-09-13 1:49 ` Joseph S. Myers
2008-09-13 17:00 ` Cary Coutant [this message]
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=c17be2b30809130959k71701590l5ebd8445e8ef75b5@mail.gmail.com \
--to=ccoutant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.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