From: Fred Fish <fnf@specifix.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, fnf@specifix.com
Subject: Re: Fix PR breakpoints/2080
Date: Mon, 20 Feb 2006 13:58:00 -0000 [thread overview]
Message-ID: <200602200859.00060.fnf@specifix.com> (raw)
In-Reply-To: <200602141545.k1EFjeGb005665@elgar.sibelius.xs4all.nl>
On Tuesday 14 February 2006 10:45, Mark Kettenis wrote:
> This fixes the testcase I checked in yesterday, so I committed it.
>
> Fred, can you check whether this also fixes your problem?
Sorry this took so long. I updated my source tree, rebuilt the tools,
and reran the gdb tests with the native Fedora Core 4 compiler and the
latest development gcc. Both got 72 unexpected failures, with only
minor differences in the results due to the fact that I didn't build
and install an objective C compiler. Prior to your gdb changes, I was
getting somewhere around 150 unexpected failures if I recall
correctly.
-Fred
prev parent reply other threads:[~2006-02-20 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 15:45 Mark Kettenis
2006-02-14 15:52 ` Daniel Jacobowitz
2006-02-14 16:39 ` Mark Kettenis
2006-02-14 16:59 ` Daniel Jacobowitz
2006-02-14 20:23 ` Jim Blandy
2006-02-20 13:58 ` Fred Fish [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=200602200859.00060.fnf@specifix.com \
--to=fnf@specifix.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.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