From: Eli Zaretskii <eliz@gnu.org>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] [RFC] Implement printing of return values of stepped-over functions
Date: Sat, 10 Dec 2022 18:33:01 +0200 [thread overview]
Message-ID: <83edt7w75u.fsf@gnu.org> (raw)
In-Reply-To: <20221210162326.854-3-ssbssa@yahoo.de> (message from Hannes Domani via Gdb-patches on Sat, 10 Dec 2022 17:23:26 +0100)
> Date: Sat, 10 Dec 2022 17:23:26 +0100
> From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
>
> It shows the return values of all function which were stepped over
> with 'next', and puts them into convenience variables, similar to
> 'finish'.
>
> ---------
> I wonder if it should always collect the return value and put into the
> value history, even if they are not printed, similar to how 'finish' works.
>
> Or maybe make them available from python somehow (plus the function symbols),
> so it could be used e.g. in a new special TUI window.
> ---
> gdb/doc/gdb.texinfo | 11 ++++++
> gdb/infcmd.c | 91 +++++++++++++++++++++++++++++++++++++++++++++
> gdb/infrun.c | 10 ++++-
> gdb/thread-fsm.h | 11 ++++++
> 4 files changed, 122 insertions(+), 1 deletion(-)
OK for the documentation part, thanks. I think it also warrants a
NEWS entry.
prev parent reply other threads:[~2022-12-10 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221210162326.854-1-ssbssa.ref@yahoo.de>
2022-12-10 16:23 ` [PATCH 1/3] Change thread_fsm::return_value to thread_fsm::print_return_values Hannes Domani
2022-12-10 16:23 ` [PATCH 2/3] Move return_value_info and refactor code setting its members Hannes Domani
2022-12-10 16:23 ` [PATCH 3/3] [RFC] Implement printing of return values of stepped-over functions Hannes Domani
2022-12-10 16:33 ` Eli Zaretskii [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=83edt7w75u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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).