From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Cc: Jason R Thorpe <thorpej@wasabisystems.com>
Subject: Re: cross-debugging of userland core files, nat -> tdep
Date: Wed, 10 Apr 2002 19:16:00 -0000 [thread overview]
Message-ID: <20020410221635.A7369@nevyn.them.org> (raw)
In-Reply-To: <20020410191229.E22095@dr-evil.shagadelic.org>
On Wed, Apr 10, 2002 at 07:12:29PM -0700, Jason R Thorpe wrote:
> On Wed, Apr 10, 2002 at 09:58:24PM -0400, Daniel Jacobowitz wrote:
>
> > Hit the nail on the head. I believe I've gotten BFD to understand ELF
> > core files appropriately for a fair number of targets; you may need to
> > add a platform-specific chunk to all the ones I didn't get to. Then
> > move supply_* out of the nat files, and link in the core code.
>
> Okay, cool.
>
> BTW, all of NetBSD's ELF core file handling is in bfd/elf.c. It
> doesn't require any platform-specific handling except one small
> switch statement to comute the note type number correctly for
> various arch's, which is in elfcore_grok_netbsd_note().
Thus the "may" :)
> > Now, if you've got time, there's a much better way to do this. The
> > "magic" supply_* and fetch_* names need to go; we should instead have a
> > table of regset types, sizes, and fetch/supply functions. I just
> > haven't gotten around to actually doing that.
>
> Heh, you said "time" :-)
Yeah, I know, I know.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-11 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 18:39 Jason R Thorpe
2002-04-10 18:58 ` Daniel Jacobowitz
2002-04-10 19:12 ` Jason R Thorpe
2002-04-10 19:16 ` Daniel Jacobowitz [this message]
2002-04-11 14:39 ` Michael Snyder
2002-04-10 23:01 ` Andrew Cagney
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=20020410221635.A7369@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=thorpej@wasabisystems.com \
/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