From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 0/2] Fix gdb.base/frame-view.exp on AArch64
Date: Mon, 30 Jan 2023 15:02:47 -0500 [thread overview]
Message-ID: <20230130200249.131155-1-simon.marchi@efficios.com> (raw)
As reported here:
https://inbox.sourceware.org/gdb-patches/df23963e-1072-90bc-dce4-af68eae2422a@polymtl.ca/T/#m56264871060c1a86f2a93e9f56d6a78c546045ae
... the test gdb.base/frame-view.exp fails on AArch64. The failure
exposes some conceptual flaw with sentinal frames of user-created
frames. This series (mostly patch #2) tries to fix it.
Simon Marchi (2):
gdb: call frame unwinders' dealloc_cache methods through destroying
the frame cache
gdb: give sentinel for user frames distinct IDs, register sentinel
frames to the frame cache
gdb/frame-id.h | 10 +++--
gdb/frame.c | 102 +++++++++++++++++++++++++++++++------------
gdb/frame.h | 10 +++++
gdb/sentinel-frame.c | 5 ++-
4 files changed, 94 insertions(+), 33 deletions(-)
--
2.39.1
next reply other threads:[~2023-01-30 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:02 Simon Marchi [this message]
2023-01-30 20:02 ` [PATCH 1/2] gdb: call frame unwinders' dealloc_cache methods through destroying the frame cache Simon Marchi
2023-02-09 7:40 ` Tom de Vries
2023-02-09 12:42 ` Tom de Vries
2023-02-09 19:53 ` Simon Marchi
2023-01-30 20:02 ` [PATCH 2/2] gdb: give sentinel for user frames distinct IDs, register sentinel frames to " Simon Marchi
2023-02-07 17:02 ` Alexandra Petlanova Hajkova
2023-02-08 21:37 ` Simon Marchi
2023-02-08 17:05 ` Luis Machado
2023-02-08 21:38 ` Simon Marchi
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=20230130200249.131155-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.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).