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: PING: PATCH: PR backtrace/14646: [x32] backtrace doesn't work
Date: Mon, 15 Oct 2012 10:10:00 -0000	[thread overview]
Message-ID: <201210151009.q9FA9r3O027266@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <CAMe9rOoxdjss8YfB1KLFyN6unWHP2RzZVszmVsiOCjrAiDqrUw@mail.gmail.com>	(hjl.tools@gmail.com)

> Date: Tue, 9 Oct 2012 09:38:32 -0700
> From: "H.J. Lu" <hjl.tools@gmail.com>
> 
> The current GDB doesn't work on x32.  This patch:
> 
> http://sourceware.org/ml/gdb-patches/2012-09/msg00714.html
> 
> isn't perfect where $pc/$sp is displayed as 64-bit integer.  But
> otherwise, GDB works fine.

Finally found some time to dig a little bit deeper.  The x32 ABI isn't
the only 32-bit ABI with 64-bit registers.  The mips n32 ABI has
exactly the same issue.  The relevant code there carries the following
comment:

  /* Use pointer types for registers if we can.  For n32 we can not,
     since we do not have a 64-bit pointer type.  */

So I'd say that you should probably commit the diff in:

   <http://sourceware.org/ml/gdb-patches/2012-09/msg00714.html>

on the grounds that other 32-bit on 64-bit ABIs also punt on the issue.

But it would be good to try to come up with a way to print 64-bit
registers as pointers for this class of ABIs.  But that should almost
certainly done by fixing target-independent parts of GDB and not by
adding more complexity to the target descriptions like your last
couple of diffs did.


  reply	other threads:[~2012-10-15 10:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 15:26 H.J. Lu
2012-10-03 15:43 ` Mark Kettenis
2012-10-03 15:59   ` H.J. Lu
2012-10-03 17:03     ` H.J. Lu
2012-10-05  2:08       ` H.J. Lu
     [not found] ` <20121003154712.GH3028@adacore.com>
     [not found]   ` <CAMe9rOreX6NAf08vD8=k4LBGevvTFUd-tqwwWmbsA3iRxxsE2A@mail.gmail.com>
     [not found]     ` <201210040657.q946vJlc006566@glazunov.sibelius.xs4all.nl>
     [not found]       ` <CAMe9rOounZ9e14QeMLvXR64gG5rJxQ9nNxt64YoLW54bx5VtHw@mail.gmail.com>
2012-10-08 19:48         ` Mark Kettenis
2012-10-08 20:04           ` H.J. Lu
2012-10-08 20:22             ` Mark Kettenis
2012-10-08 20:38               ` H.J. Lu
2012-10-08 20:47                 ` Mark Kettenis
2012-10-08 21:01                   ` H.J. Lu
2012-10-09 15:32                     ` H.J. Lu
2012-10-09 15:40                       ` Mark Kettenis
2012-10-09 15:48                         ` Mark Kettenis
2012-10-09 16:35                           ` H.J. Lu
2012-10-09 16:38                             ` H.J. Lu
2012-10-15 10:10                               ` Mark Kettenis [this message]
2012-10-15 20:41                                 ` H.J. Lu
2012-10-11 22:34                           ` H.J. Lu
2012-10-12  8:31                             ` Mark Kettenis

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=201210151009.q9FA9r3O027266@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