From: Simon Marchi <simark@simark.ca>
To: Lancelot SIX <lancelot.six@amd.com>, gdb-patches@sourceware.org
Cc: lsix@lancelotsix.com
Subject: Re: [PATCH v3 1/2] gdb: add a symbol* argument to get_return_value
Date: Wed, 2 Feb 2022 16:01:15 -0500 [thread overview]
Message-ID: <8ebbde37-0acc-c430-ea36-d21c14163ef8@simark.ca> (raw)
In-Reply-To: <20220202184115.83396-2-lancelot.six@amd.com>
On 2022-02-02 1:41 p.m., Lancelot SIX via Gdb-patches wrote:
> Add an argument to the get_return_value function to indicate the symbol
> of the function the debuggee is returning from. This will be used by
> the following patch.
>
> No user visible change after this patch.
>
> Tested on x86_64-linux.
>
> Change-Id: Idf1279f1f7199f5022738a6679e0fa63fbd22edc
> ---
> gdb/infcmd.c | 5 +++--
> gdb/inferior.h | 3 ++-
> gdb/python/py-finishbreakpoint.c | 29 ++++++++++++++++++++---------
> 3 files changed, 25 insertions(+), 12 deletions(-)
>
> diff --git a/gdb/infcmd.c b/gdb/infcmd.c
> index 994dd5b32a3..66667d67b21 100644
> --- a/gdb/infcmd.c
> +++ b/gdb/infcmd.c
> @@ -1410,7 +1410,8 @@ advance_command (const char *arg, int from_tty)
> right after an inferior call has finished. */
>
> struct value *
> -get_return_value (struct value *function, struct type *value_type)
> +get_return_value (struct symbol *func_symbol, struct value *function,
> + struct type *value_type)
get_return_value's comment (above this) is quite out of date, referring things
that don't exist anymore. While at it, can you update it, move it to the header
file, and add the /* See ... */ comment here?
Simon
next prev parent reply other threads:[~2022-02-02 21:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 18:41 [PATCH v3 0/2] Make GDB respect the DW_CC_nocall attribute Lancelot SIX
2022-02-02 18:41 ` [PATCH v3 1/2] gdb: add a symbol* argument to get_return_value Lancelot SIX
2022-02-02 21:01 ` Simon Marchi [this message]
2022-02-02 21:59 ` [PATCH v4] " Lancelot SIX
2022-02-03 1:03 ` Simon Marchi
2022-02-03 11:10 ` Six, Lancelot
2022-02-03 12:35 ` Simon Marchi
2022-02-03 15:46 ` Lancelot SIX
2022-02-03 18:28 ` [PATCH v5] " Lancelot SIX
2022-02-03 19:26 ` Simon Marchi
2022-02-03 22:34 ` Six, Lancelot
2022-02-02 18:41 ` [PATCH v3 2/2] gdb: Respect the DW_CC_nocall attribute Lancelot SIX
2022-02-08 14:27 ` Simon Marchi
2022-02-15 10:53 ` Lancelot SIX
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=8ebbde37-0acc-c430-ea36-d21c14163ef8@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=lsix@lancelotsix.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).