public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/14673] Pseudo registers aren't updated in stack unwind
Date: Thu, 14 Dec 2023 16:46:24 +0000	[thread overview]
Message-ID: <bug-14673-4717-vnresxG6x9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14673-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14673

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
I believe this is fixed by my pseudo register series, that commit and the 20 or
so previous ones:

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f5d420bbceeb1d5065c3d91dd7c6c1e43f855ca1

When running:

./gdb -batch -nx -q --data-directory=data-directory test \                      
    -ex 'b foo' -ex r -ex bt \
    -ex 'frame 0' \
    -ex 'p/x $sp' -ex 'p/x $rsp' -ex 'p/x $esp' \
    -ex 'frame 1' \
    -ex 'p/x $sp' -ex 'p/x $rsp' -ex 'p/x $esp'

Before, I get:

    #0  foo (x=2) at test.c:3
    3         return x + 1;
    $1 = 0x7fffffffe180
    $2 = 0x7fffffffe180
    $3 = 0xffffe180

    #1  0x0000555555555146 in main () at test.c:8
    8         foo(2);
    $4 = 0x7fffffffe190
    $5 = 0x7fffffffe190
    $6 = 0xffffe180

After, I get:

    #0  foo (x=2) at test.c:3
    3         return x + 1;
    $1 = 0x7fffffffe180
    $2 = 0x7fffffffe180
    $3 = 0xffffe180

    #1  0x0000555555555146 in main () at test.c:8
    8         foo(2);
    $4 = 0x7fffffffe190
    $5 = 0x7fffffffe190
    $6 = 0xffffe190

From what I can tell, from amd64-tdep.c, the eip pseudo register exists only on
the x32 arch, which I can't test.  But if it's handled like all other dword
pseudo registers, it should work as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-12-14 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05  1:19 [Bug tdep/14673] New: esp isn't " hjl.tools at gmail dot com
2012-10-05  2:07 ` [Bug tdep/14673] Pseudo registers aren't " hjl.tools at gmail dot com
2023-12-14 16:46 ` simark at simark dot ca [this message]
2023-12-15 16:43 ` tromey at sourceware dot org

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=bug-14673-4717-vnresxG6x9@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).