From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] Reimplement DAP backtrace using frame filters
Date: Wed, 14 Jun 2023 10:30:46 -0600 [thread overview]
Message-ID: <20230614-dap-frame-decor-v1-0-af87db6467b2@adacore.com> (raw)
This series reimplements DAP backtraces using frame filters. This
seemed nice to have, because it would present users with a friendlier
view into the stack. It also turned out to simplify the code a bit.
---
Tom Tromey (5):
Fix execute_frame_filters doc string
Add new interface to frame filter iteration
Fix oversights in frame decorator code
Simplify FrameVars
Reimplement DAP stack traces using frame filters
gdb/python/lib/gdb/FrameDecorator.py | 44 ++++++-------------
gdb/python/lib/gdb/dap/bt.py | 81 +++++++++++++++--------------------
gdb/python/lib/gdb/dap/evaluate.py | 11 ++---
gdb/python/lib/gdb/dap/frames.py | 7 +++
gdb/python/lib/gdb/dap/scopes.py | 83 ++++++++++++++----------------------
gdb/python/lib/gdb/frames.py | 83 +++++++++++++++++++++++++-----------
6 files changed, 152 insertions(+), 157 deletions(-)
---
base-commit: 63224e96d0cd9e726bcd1d6d512255d92b7c5317
change-id: 20230614-dap-frame-decor-5cccd7f34dd3
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2023-06-14 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 16:30 Tom Tromey [this message]
2023-06-14 16:30 ` [PATCH 1/5] Fix execute_frame_filters doc string Tom Tromey
2023-06-14 16:30 ` [PATCH 2/5] Add new interface to frame filter iteration Tom Tromey
2023-06-14 16:30 ` [PATCH 3/5] Fix oversights in frame decorator code Tom Tromey
2023-06-14 16:30 ` [PATCH 4/5] Simplify FrameVars Tom Tromey
2023-06-22 16:09 ` Tom Tromey
2023-06-14 16:30 ` [PATCH 5/5] Reimplement DAP stack traces using frame filters 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=20230614-dap-frame-decor-v1-0-af87db6467b2@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).