public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/29357] gdb for golang prints wrong frame info at the ret instruction
Date: Fri, 31 Mar 2023 00:05:25 +0000	[thread overview]
Message-ID: <bug-29357-4717-cbcW4Oxz2u@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29357-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I think this was fixed.  There were some epilogue changes in the recent
past that probably did it.

Here you can see that the CFA at the start of main.main and at the ret
are now the same:

Thread 1 "main" hit Breakpoint 1, main.main () at
/home/tromey/gdb/PRS/go-29357/main.go:5
5       func main() {
(gdb) info frame
Stack level 0, frame at 0xc000106f80:
 rip = 0x480fa6 in main.main (/home/tromey/gdb/PRS/go-29357/main.go:5); saved
rip = 0x433ff2
 source language unknown.
 Arglist at 0xc000106f70, args: 
 Locals at 0xc000106f70, Previous frame's sp is 0xc000106f80
 Saved registers:
  rip at 0xc000106f78
(gdb) c
Continuing.
hello world

Thread 1 "main" hit Breakpoint 3, 0x0000000000480ffb in main.main () at
/home/tromey/gdb/PRS/go-29357/main.go:7
7       }
(gdb) info frame
Stack level 0, frame at 0xc000106f80:
 rip = 0x480ffb in main.main (/home/tromey/gdb/PRS/go-29357/main.go:7); saved
rip = 0x433ff2
 source language unknown.
 Arglist at 0xc000106f70, args: 
 Locals at 0xc000106f70, Previous frame's sp is 0xc000106f80
 Saved registers:
  rip at 0xc000106f78
(gdb) pipe disassemble | grep -e '=>'
=> 0x0000000000480ffb <+91>:    ret

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

      parent reply	other threads:[~2023-03-31  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  2:37 [Bug go/29357] New: " greyschwinger at gmail dot com
2022-07-12  2:38 ` [Bug go/29357] " greyschwinger at gmail dot com
2023-03-31  0:05 ` tromey at sourceware dot org [this message]

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-29357-4717-cbcW4Oxz2u@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).