From: Mark Kettenis <kettenis@chello.nl>
To: drow@mvista.com
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] Core files and the architecture vector
Date: Sat, 11 Oct 2003 22:43:00 -0000 [thread overview]
Message-ID: <200310112242.h9BMgiMI010470@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20031011222622.GB7209@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 11 Oct 2003 18:26:22 -0400)
Date: Sat, 11 Oct 2003 18:26:22 -0400
From: Daniel Jacobowitz <drow@mvista.com>
I'll respond to the rest of your message later but...
On Sun, Oct 12, 2003 at 12:07:32AM +0200, Mark Kettenis wrote:
> Let me elaborate on the second point. When a 32-bit executable
> running on FreeBSD/amd64 or GNU/Linux x86-64 dumps, it produces an
> 64-bit ELF core file. To be able to make any sense out of this core
> file, we'll need the 64-bit register set definitions that are provided
> by the regset_from_core_section method from the 64-bit architecture
I still don't think this bit makes much sense. The process sees only
32-bit registers; the core should contain only 32-bit registers.
Well, it's not for me to decide what how the various OSes dump core
:-(.
Anyway even for 32-bit only stuff the core file architecture and
executable architecture might differ. When running a GNU/Linux i386
binary on FreeBSD/i386, it produces a FreeBSD/i386 corefile.
Do we see 32-bit or 64-bit registers from ptrace when debugging such a
process?
At least on FreeBSD/amd64 you see the 64-bit register with ptrace.
Mark
next prev parent reply other threads:[~2003-10-11 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 22:07 Mark Kettenis
2003-10-11 22:26 ` Daniel Jacobowitz
2003-10-11 22:43 ` Mark Kettenis [this message]
2003-10-11 23:57 ` Andrew Cagney
2003-10-13 13:44 ` Paul Koning
2003-10-11 23:07 ` 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=200310112242.h9BMgiMI010470@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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