From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "David S. Miller" <davem@davemloft.net>
Cc: drow@false.org, gdb@sources.redhat.com
Subject: Re: core regs vs. proc-service regs mess
Date: Wed, 05 Apr 2006 08:25:00 -0000 [thread overview]
Message-ID: <12186.192.87.1.22.1144225521.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20060405.000621.41243752.davem@davemloft.net>
>
> In trying to get core files working properly again on Linux/Sparc and
> Daniel I now see the problems you referred to the other day.
>
> What we have currently on Linux/Sparc is:
>
> 1) ptrace() interfaces have one layout for regsets
> 2) ELF core files store regsets in a different
> format
>
> Now proc-service.c wants fill_gregset() et al. to
> provide things in the ptrace() style layout, that is
> what libthread_db expects under Linux.
>
> But linux_nat_make_corefile_notes() expects the fill_gregset()
> et al. to provide ELF core file format registers.
Hi Dave,
Yes this is annoying, and ultimately caused because the ptrace(2) and
core(5) interfaces on Linux were never properly designed (heck they're not
even fully documented) and inconsistent between the different hardware
platforms. For most platforms the ptrace(2) and core(5) layout are the
same, but not on sparc (presumably because ptrace(2) on sparc tries to
be compatible with SunOS/Solaris).
> This is completely contradictory, and I don't have any idea how to
> cleanly resolve this outside of duplicating the entirety of
> linux_nat_make_corefile_notes() on Linux/Sparc which is silly.
>
> Daniel any ideas? :-) Maybe we can have a "linux_tdep" struct where we
> can place a "->to_fill_core_gregset()" type method or similar?
What really should happen is to convert linux_nat_make_corefile_notes() to
use the regset_from_core_section() interface. Unfortunately that is quite
a bit of work since most Linux targets don't provide that interface yet.
Mark
next prev parent reply other threads:[~2006-04-05 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 7:07 David S. Miller
2006-04-05 8:25 ` Mark Kettenis [this message]
2006-04-05 13:23 ` Daniel Jacobowitz
2006-04-06 1:10 ` David S. Miller
2006-04-06 13:15 ` David S. Miller
2006-04-06 13:38 ` Daniel Jacobowitz
2006-04-07 0:35 ` David S. Miller
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=12186.192.87.1.22.1144225521.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=davem@davemloft.net \
--cc=drow@false.org \
--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