From: Daniel Jacobowitz <drow@false.org>
To: Jon Ringle <jon.ringle@comdial.com>
Cc: gdb@sources.redhat.com, m.m.kettenis@alumnus.utwente.nl
Subject: Re: arm core analysis on x86 host
Date: Thu, 31 Mar 2005 14:28:00 -0000 [thread overview]
Message-ID: <20050331142946.GA1807@nevyn.them.org> (raw)
In-Reply-To: <200503310908.05826.jon.ringle@comdial.com>
On Thu, Mar 31, 2005 at 09:08:05AM -0500, Jon Ringle wrote:
> On Wednesday 30 March 2005 13:01, Mark Kettenis wrote:
> > The core file should somehow be tagged as Linux. Â If it is not tagged
> > as such, how are we going to interpret it? Â The fact that it is an ELF
> > core file, and has notes like NT_PRSTATUS does not tell us where each
> > register is stored. Â Right now we have to guess what the layout of
> > these notes is based on the size of the sections or because the header
> > describing the layout is available because we're building a native
> > GDB.
>
> I modified my linux kernel (based on 2.2.16) in linux/fs/binfmt_elf.c to emit:
> elf.e_ident[EI_OSABI] = ELFOSABI_LINUX;
> The linux-2.6 series does this.
>
> This seemed to help in conjuction with changes to gdb/arm-linux-tdep.c to add:
> set_gdbarch_regset_from_core_section(gdbarch,arm_linux_regset_from_core_section);
>
> I can send in a patch for the arm-linux-tdep.c changes if you'd like.
It doesn't look like you have a copyright assignment on file - is that
right? In that case, give me a couple of days; once my current ARM
patch is finished, I can look into doing this myself based on our
conversation.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-31 14:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 23:29 Jon Ringle
2005-03-28 23:56 ` Daniel Jacobowitz
2005-03-29 0:48 ` Jon Ringle
2005-03-29 1:31 ` Daniel Jacobowitz
2005-03-29 4:17 ` Jon Ringle
2005-03-29 4:57 ` Daniel Jacobowitz
2005-03-29 16:19 ` Jon Ringle
2005-03-29 16:33 ` Daniel Jacobowitz
2005-03-29 16:39 ` Jon Ringle
2005-03-29 16:52 ` Daniel Jacobowitz
2005-03-29 17:18 ` Jon Ringle
2005-03-29 19:35 ` Jon Ringle
2005-03-30 2:07 ` Jon Ringle
2005-03-30 4:51 ` Daniel Jacobowitz
2005-03-30 14:42 ` Jon Ringle
2005-03-30 15:15 ` M.M. Kettenis
2005-03-30 15:25 ` Daniel Jacobowitz
2005-03-30 18:02 ` Mark Kettenis
2005-03-30 18:18 ` Daniel Jacobowitz
2005-03-31 14:08 ` Jon Ringle
2005-03-31 14:28 ` Daniel Jacobowitz [this message]
2005-03-31 14:35 ` Jon Ringle
2005-04-06 22:16 ` Jon Ringle
2005-04-06 22:27 ` 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=20050331142946.GA1807@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jon.ringle@comdial.com \
--cc=m.m.kettenis@alumnus.utwente.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