From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [rfa] Cross corefile support for ARM
Date: Fri, 23 Jun 2006 12:42:00 -0000 [thread overview]
Message-ID: <20060623124216.GA17098@nevyn.them.org> (raw)
In-Reply-To: <20060608152432.GA20630@nevyn.them.org>
On Thu, Jun 08, 2006 at 11:24:32AM -0400, Daniel Jacobowitz wrote:
> I've reimplemented ARM Linux corefile support to use the new interfaces, and
> work for cross-debuggers. I needed this last week to track down a problem
> in an EABI binary and I didn't have an EABI native GDB available.
>
> I've tested it manually in both cross and native configurations; it actually
> fixes FPA (NWFPE) support for core files, which had gotten broken at some
> point in the past when ARM stopped providing FP0_REGNUM.
>
> This whole story is a bit of an embarrassment. I've implemented this at
> least twice in the past but never cleaned it up enough to submit it. And
> Girish Shilamkar submitted something similar in February, although I didn't
> notice at the time that (A) he didn't remove the existing core file support
> in arm-linux-nat.c, which would probably break native ARM gdbs, and (B) the
> FP support was bogus and didn't match any core dump layout I'm famliar with.
> And I never heard back about TimeSys's copyright assignment, so that's been
> sitting in limbo.
>
> Look OK?
Hi Richard,
Did you notice:
http://sourceware.org/ml/gdb-patches//2006-06/msg00071.html
(Needed it again today :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-23 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 15:24 Daniel Jacobowitz
2006-06-23 12:42 ` Daniel Jacobowitz [this message]
2006-06-23 13:36 ` Richard Earnshaw
2006-07-12 20:46 ` 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=20060623124216.GA17098@nevyn.them.org \
--to=drow@false.org \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sourceware.org \
/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