Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: hjl.tools@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: PR corefiles/11511: gcore doesn't work with orig_rax on  	Linux/amd64
Date: Sun, 18 Apr 2010 21:33:00 -0000	[thread overview]
Message-ID: <201004182132.o3ILWqtn029873@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <z2q6dc9ffc81004171150z164a5fb2y727e835914421f6b@mail.gmail.com> 	(hjl.tools@gmail.com)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]

> Date: Sat, 17 Apr 2010 11:50:11 -0700
> From: "H.J. Lu" <hjl.tools@gmail.com>
> 
> On Sat, Apr 17, 2010 at 9:25 AM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> >> Date: Sat, 17 Apr 2010 09:11:15 -0700
> >> From: "H.J. Lu" <hongjiu.lu@intel.com>
> >>
> >> This patch adds orig_rax support to amd64_linux_gregset_reg_offset.
> >> amd64 has both tdep->gregset_reg_offset/tdep->gregset_num_regs and
> >> amd64_native_gregset64_reg_offset/amd64_native_gregset64_num_regs.  They
> >> are identical. There is no need to keep both.  This patch also removes
> >> amd64_native_gregset64_reg_offset/amd64_native_gregset64_num_regs. OK
> >> to install?
> >
> > No.  I want to keep the -nat.c and -tdep.c code separate.
> 
> Can I replace amd64_linux_gregset64_reg_offset with
> amd64_linux_gregset_reg_offset, like amd64nbsd-nat.c
> and amd64obsd-nat.c?

We can discuss that, yes.  The way the code is organized now, at least
native debugging will continue to work if the layout of the trap frame
in the Linux kernel were to change.  At least in the past there was
some fear that this would happen.  That danger is probably small; I'm
not even sure if the data structure for PTRACE_GETREGS is even linked
to the trap frame layout anymore.

Of course the benefit of doing so is that if the kernel ABI is ever
broken GDB will completely stop working on Linux instead of just being
partly broken.

Any other people have an opinion about this?


  reply	other threads:[~2010-04-18 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 16:11 H.J. Lu
2010-04-17 16:25 ` Mark Kettenis
2010-04-17 18:50   ` H.J. Lu
2010-04-18 21:33     ` Mark Kettenis [this message]
2010-04-19 15:26       ` Daniel Jacobowitz
2010-04-19 17:21       ` H.J. Lu
2010-04-19 17:28         ` H. Peter Anvin
2010-04-20 22:17           ` Roland McGrath

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=201004182132.o3ILWqtn029873@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.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