From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Use frame.name() in FrameDecorator
Date: Tue, 1 Aug 2023 14:06:27 -0600 [thread overview]
Message-ID: <20230801200627.2901739-1-tromey@adacore.com> (raw)
A co-worker pointed out that gdb's DAP implementation might return an
integer for the name of a stack frame, like:
{"id": 1, "name": 93824992310799, ...}
This can be seen currently in the logs of the bt-nodebug.exp test
case.
What is happening is that FrameDecorator falls back on returning the
PC when the frame's function symbol cannot be found, relying on the
gdb core to look up the minsym and print its name.
This can actually yield the wrong answer sometimes, because it falls
into the get_frame_pc / get_frame_address_in_block problem -- if the
frame is at a call to a noreturn function, the PC in this case might
appear to be in the next function in memory. For more on this, see:
https://sourceware.org/bugzilla/show_bug.cgi?id=8416
and related bugs.
However, there's a different approach we can take: the code here can
simply use Frame.name. This handles the PC problem correctly, and
gets us the information we need.
---
gdb/python/lib/gdb/FrameDecorator.py | 15 ++++-----------
gdb/testsuite/gdb.dap/bt-nodebug.exp | 9 ++++++++-
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gdb/python/lib/gdb/FrameDecorator.py b/gdb/python/lib/gdb/FrameDecorator.py
index aa9a2201bec..39ee2e2547c 100644
--- a/gdb/python/lib/gdb/FrameDecorator.py
+++ b/gdb/python/lib/gdb/FrameDecorator.py
@@ -75,17 +75,10 @@ class _FrameDecoratorBase(object):
elif frame.type() == gdb.SIGTRAMP_FRAME:
return "<signal handler called>"
- func = frame.function()
-
- # If we cannot determine the function name, return the
- # address. If GDB detects an integer value from this function
- # it will attempt to find the function name from minimal
- # symbols via its own internal functions.
- if func is None:
- pc = frame.pc()
- return pc
-
- return str(func)
+ func = frame.name()
+ if not isinstance(func, str):
+ func = "???"
+ return func
def address(self):
"""Return the address of the frame's pc"""
diff --git a/gdb/testsuite/gdb.dap/bt-nodebug.exp b/gdb/testsuite/gdb.dap/bt-nodebug.exp
index e4dcef35a67..e9726d2e17d 100644
--- a/gdb/testsuite/gdb.dap/bt-nodebug.exp
+++ b/gdb/testsuite/gdb.dap/bt-nodebug.exp
@@ -44,6 +44,13 @@ lassign [dap_wait_for_event_and_check "stopped at function breakpoint" stopped \
"body hitBreakpointIds" $fn_bpno] unused objs
# The bug was that this request would fail.
-dap_check_request_and_response "backtrace" stackTrace {o threadId [i 1]}
+set obj [dap_check_request_and_response "backtrace" \
+ stackTrace {o threadId [i 1]}]
+set frames [dict get [lindex $obj 0] body stackFrames]
+
+gdb_assert {[llength $frames] == 3} "three frames"
+
+gdb_assert {[dict get [lindex $frames 1] name] == "no_debug_info"} \
+ "name of no-debug frame"
dap_shutdown
--
2.40.1
next reply other threads:[~2023-08-01 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 20:06 Tom Tromey [this message]
2023-08-03 13:50 ` Alexandra Petlanova Hajkova
2023-08-03 15:36 ` Tom Tromey
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=20230801200627.2901739-1-tromey@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@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).