From: Andrew Cagney <ac131313@cygnus.com>
To: thorpej@wasabisystems.com
Cc: gdb@sources.redhat.com
Subject: Re: cross-debugging of userland core files, nat -> tdep
Date: Wed, 10 Apr 2002 23:01:00 -0000 [thread overview]
Message-ID: <3CB526B4.8090807@cygnus.com> (raw)
In-Reply-To: <20020410183918.C22095@dr-evil.shagadelic.org>
> Hi folks...
>
> I've been thinking of what needs to happen in order to support
> cross-debugging of userland core files in NetBSD.
>
> BFD can already handle NetBSD ELF core files in the appropriate way. As
> far as I can tell, the only stumbling block is getting GDB to play nicely
> with them.
>
> The problem is that the functions that supply registers, etc. from the core
> file are all in "nat" modules. This is probably mostly an artifact of the
> data being in the same format as the reg structure returned by ptrace(2).
>
> What I'd like to do is move those supply-registers routines into an
> appropriate "tdep" file. They can still be used by the "nat" routines
> which use ptrace(2), and all the core file handling goo can then go into
> the "tdep" module, as well.
>
> If this sounds reasonable, then I'll start my little project. Otherwise,
> I'd love to hear suggestions :-)
>
> Thanks.
Have a look at sparc-tdep.c:supply_fpregset(). Depending on how
``pure'' your elf core files are you could do similar. If not
archnbsd-tdep.c sounds promising.
There is a namespace problem here (these methods most likely also need
to be multi-arched in someway, but that is a separate story).
Andrew
prev parent reply other threads:[~2002-04-11 6:01 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
2002-04-11 14:39 ` Michael Snyder
2002-04-10 23:01 ` Andrew Cagney [this message]
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=3CB526B4.8090807@cygnus.com \
--to=ac131313@cygnus.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