From: Thomas Schwinge <thomas@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>, <bug-hurd@gnu.org>
Subject: Re: [PATCH,HURD] Fix reading core
Date: Thu, 11 Apr 2013 02:44:00 -0000 [thread overview]
Message-ID: <87fvyyggkc.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20130409234117.GC24389@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
Hi!
On Tue, 9 Apr 2013 16:41:17 -0700, Joel Brobecker <brobecker@adacore.com> wrote:
> > The i386 GNU/Hurd ELF core format actually follows the uaccess gregset_t
> > array format, not the Mach thread state format. This fixes gdb reading
> > it.
> >
> > * gdb/i386gnu-nat.c (CREG_OFFSET): New macro.
> > (creg_offset): New array.
> > (CREG_ADDR): Use creg_offset instead of reg_offset.
>
> Did anyone review this? I don't know GNU/Hurd, but the patch looks
> very plausible.
Not yet, but it's on my list... (together with other Hurd GDB work).
Anyway, Joel, thanks for following up on Samuel's patch, and not letting
it fall through the cracks!
> Do you have write access to the GDB repository? If not, do you have
> copyright assignment papers on file? This patch is small enough that
> we can take it as a tiny patch, but if you think you're going to
> send more patches, we should probably get you started on those.
I'd support all that; Samuel's not on file for GDB (but is for other
packages, such as Hurd proper).
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-04-10 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 2:01 Samuel Thibault
2013-04-10 11:33 ` Joel Brobecker
2013-04-11 2:44 ` Thomas Schwinge [this message]
2013-04-11 3:55 ` Samuel Thibault
2013-04-11 14:08 ` Thomas Schwinge
2013-04-26 17:50 ` Samuel Thibault
2013-04-26 19:02 ` Joel Brobecker
2013-04-26 19:03 ` Alfred M. Szmidt
2013-04-30 12:02 ` Thomas Schwinge
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=87fvyyggkc.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=bug-hurd@gnu.org \
--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