From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb@sources.redhat.com
Subject: Re: Question about ELF core file sections
Date: Wed, 16 Nov 2005 15:49:00 -0000 [thread overview]
Message-ID: <20051116154942.GA13434@nevyn.them.org> (raw)
In-Reply-To: <437B53B4.5000906@tausq.org>
On Wed, Nov 16, 2005 at 11:43:48PM +0800, Randolph Chung wrote:
> I'm trying to get core file support working on hppa64-hp-hpux11.11. I'm
> trying to reuse the infrastructure from corelow.c and the "new"
> regset_from_core_section() interface, but I'm a bit confused about how
> it's supposed to work.
>
> corelow.c:get_core_registers() is hardcoded to look for registers in
> sections ".reg", ".reg2", ".reg-xfp" -- are these section names somehow
> standard? I don't find these documented in the ELF specs. I see that on
> Linux variants, this ".reg" section is actually synthesized by bfd. This
> all seems to be a bit convoluted :(
They aren't section names at all. Core files don't have sections, only
segments. They're a purely BFD-internal convention.
> On HPUX, there is a program header type HP_CORE_PROC that points to a
> datastructure with the register info. Is there anyway to use the
> existing interface to get to this info? If not, it looks like I can get
> it to work using core_vec, but that uses an interface that is marked
> deprecated....
You play the same tricks in BFD that ELF does, probably :-)
Alternatively you query the program headers to do it, but the existing
GDB<->BFD interface is very section-oriented.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-16 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 15:43 Randolph Chung
2005-11-16 15:49 ` Daniel Jacobowitz [this message]
2005-11-16 16:14 ` Mark Kettenis
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=20051116154942.GA13434@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=randolph@tausq.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