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, 08 Oct 2012 20:22:00 -0000 [thread overview]
Message-ID: <201210082022.q98KM82d014759@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <CAMe9rOpU6+oRN=a5xxK4pZhnyET2v7mu0UzCXo=HrAdQnVqgig@mail.gmail.com> (hjl.tools@gmail.com)
> Date: Mon, 8 Oct 2012 13:04:03 -0700
> From: "H.J. Lu" <hjl.tools@gmail.com>
>
> On Mon, Oct 8, 2012 at 12:48 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> >> Date: Thu, 4 Oct 2012 06:57:22 -0700
> >> From: "H.J. Lu" <hjl.tools@gmail.com>
> >>
> >> On Wed, Oct 3, 2012 at 11:57 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> >> >
> >> > Perhaps the user-regs.c mechanism can be used to establish eip -> pc
> >> > and esp -> sp mappings?
> >>
> >> It doesn't help as long as gdbarch_pc_regnum/gdbarch_sp_regnum
> >> are used for both frame pc/sp value and unwind pc/sp value. For x32,
> >> we want eip/esp for frame pc/sp value and rip/rsp for unwind pc/sp
> >> value.
> >
> > That probably means we need to set gdbarch_pc_regnum (and
> > gdbarch_sp_regnum) to -1 for x32.
>
> We can't set gdbarch_pc_regnum/gdbarch_sp_regnum to -1:
>
>
> GNU gdb (GDB) 7.5.50.20121008-cvs
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-unknown-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from
> /export/build/gnu/glibc-x32/build-x86_64-linux/elf/sln...done.
> (gdb) b main
> Breakpoint 1 at 0x400c20: file sln.c, line 50.
> (gdb) r
> Starting program: /export/build/gnu/glibc-x32/build-x86_64-linux/elf/sln
> /export/gnu/import/git/gdb/gdb/regcache.c:1062: internal-error:
> regcache_read_pc: Unable to find PC
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n)
Well, obviously you'll need to implement gdbarch_read_pc() for this to
work. And probably a few more gdbarch methods.
next prev parent reply other threads:[~2012-10-08 20:22 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 [this message]
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
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=201210082022.q98KM82d014759@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