From: Pedro Alves <pedro@palves.net>
To: "Torbjörn SVENSSON" <torbjorn.svensson@foss.st.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/arm: Stop unwinding on error, but do not assert
Date: Thu, 13 Oct 2022 12:21:46 +0100 [thread overview]
Message-ID: <9cc66b68-94b4-ed24-f4b5-93a441b8a70d@palves.net> (raw)
In-Reply-To: <20221013091740.645783-1-torbjorn.svensson@foss.st.com>
On 2022-10-13 10:17 a.m., Torbjörn SVENSSON via Gdb-patches wrote:
> + /* Unwind of this frame is not possible. Return outer_frame_id to stop the
> + unwinding. */
> + if (cache == NULL)
> + {
> + *this_id = outer_frame_id;
> + return;
> + }
Please let's not add more uses of outer_frame_id if we can avoid it. We're getting
close to eliminating it. Can a cache object still be returned, and then a frame id
be successfully computed?
You can stop the unwinding in some other way. For example, arm_m_exception_cache has a few
of these:
/* Terminate any further stack unwinding by referring to self. */
arm_cache_set_active_sp_value (cache, tdep, sp);
return cache;
(Not sure exactly how that works.)
Alternatively, you can implement a frame_unwind::stop_reason callback and return
UNWIND_OUTERMOST, which is already done in arm-tdep.c in other scenarios too.
next prev parent reply other threads:[~2022-10-13 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 9:17 Torbjörn SVENSSON
2022-10-13 9:46 ` Luis Machado
2022-10-13 11:21 ` Pedro Alves [this message]
2022-10-13 12:24 ` Torbjorn SVENSSON
2022-10-13 13:25 ` Pedro Alves
2022-10-13 13:11 ` Luis Machado
2022-10-13 13:41 ` Pedro Alves
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=9cc66b68-94b4-ed24-f4b5-93a441b8a70d@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=torbjorn.svensson@foss.st.com \
/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).