From: Daniel Jacobowitz <dan@debian.org>
To: Dave Johnson <djohnson+linuxmips@sw.starentnetworks.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
Date: Sun, 28 Aug 2005 11:45:31 -0400 [thread overview]
Message-ID: <20050828154530.GA26423@nevyn.them.org> (raw)
In-Reply-To: <17162.16068.212165.340275@cortez.sw.starentnetworks.com>
On Mon, Aug 22, 2005 at 05:08:20PM -0400, Dave Johnson wrote:
>
> I've been trying to fix core file support for 64bit kernel with o32
> userspace (working against 2.6.12 cvs tag).
>
> After applying the patch posted on 13 Feb 2005 from Daniel Jacobowitz
> to fix binfmt_elfo32.c (any reason this didn't make it into CVS?),
> I still ran into trouble with gdb not understanding the NT_PRSTATUS
> header in the core file.
>
> While Dan's fix makes the kernel use elf32 definitions, gdb was still
> getting confused by pr_reg contained in the core file.
>
> Dan's definition of ELF_CORE_COPY_REGS in binfmt_elfo32.c is copying
> the registers using EF_R0 as 0 not 6 producing results into offset 0
> through 37 not 6 through 43 as gdb expects for 32bit core files.
>
> Below patch (applied after Dan's patch) writes the registers at offset
> 6 making gdb much happier.
FYI, this has all been rearranged since - it did this correctly at the
time. I don't know why the patch was dropped.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-08-28 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 21:08 gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed? Dave Johnson
2005-08-28 15:45 ` Daniel Jacobowitz [this message]
2006-01-16 16:09 ` Martin Michlmayr
2006-01-18 15:43 ` Martin Michlmayr
2006-01-18 15:51 ` Ralf Baechle
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=20050828154530.GA26423@nevyn.them.org \
--to=dan@debian.org \
--cc=djohnson+linuxmips@sw.starentnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.