From: Kevin Buettner <kevinb@redhat.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org, Tristan Gingold <gingold@ACT-Europe.FR>
Subject: Re: [RFA] Fix has_section_at_zero for separate debug files
Date: Tue, 12 Jan 2010 05:01:00 -0000 [thread overview]
Message-ID: <20100111220043.44a9449d@redhat.com> (raw)
In-Reply-To: <m3tyusnxf3.fsf@fleche.redhat.com>
On Mon, 11 Jan 2010 14:28:48 -0700
Tom Tromey <tromey@redhat.com> wrote:
> Tristan> No regression on GNU Linux i386.
>
> I wonder whether this code path is tested there.
> I don't know.
I don't know either. My earlier patch (which seems to be causing
problems on Darwin now) was motivated by some problems that I was
seeing with mep-elf.
I'll test Tristan's patch using a mep-elf build in the next few days
to see if it too solves the problems that I was seeing last year.
Kevin
next prev parent reply other threads:[~2010-01-12 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 13:09 Tristan Gingold
2010-01-11 21:29 ` Tom Tromey
2010-01-12 5:01 ` Kevin Buettner [this message]
2010-01-12 8:56 ` Tristan Gingold
2010-04-19 20:27 ` Joel Brobecker
2010-01-12 8:55 ` Tristan Gingold
2010-04-28 22:40 ` Kevin Buettner
2010-05-05 18:43 ` Joel Brobecker
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=20100111220043.44a9449d@redhat.com \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@ACT-Europe.FR \
--cc=tromey@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