From: Eli Zaretskii <eliz@gnu.org>
To: Ari Hannula <ari.hannula@intel.com>
Cc: gdb-patches@sourceware.org, tim.wiederhake@intel.com
Subject: Re: [PATCH v3 1/2] [func_call] Add function-call-history-length command to MI.
Date: Wed, 06 Jul 2022 16:45:24 +0300 [thread overview]
Message-ID: <83bku273t7.fsf@gnu.org> (raw)
In-Reply-To: <20220706133639.114681-2-ari.hannula@intel.com> (message from Ari Hannula via Gdb-patches on Wed, 6 Jul 2022 15:36:38 +0200)
> Date: Wed, 6 Jul 2022 15:36:38 +0200
> From: Ari Hannula via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Tim Wiederhake <tim.wiederhake@intel.com>
>
> From: Tim Wiederhake <tim.wiederhake@intel.com>
>
> This allows MI clients like Eclipse to retrieve the length of the function
> call history.
>
> Adds documentation for the command.
>
> Adds tests for the command.
>
> Signed-off-by: Tim Wiederhake <tim.wiederhake@intel.com>
> Signed-off-by: Ari Hannula <ari.hannula@intel.com>
> ---
> gdb/Makefile.in | 1 +
> gdb/doc/gdb.texinfo | 28 ++++++
> gdb/mi/mi-cmd-record.c | 34 +++++++
> gdb/mi/mi-cmd-record.h | 27 ++++++
> gdb/mi/mi-cmds.c | 2 +
> gdb/mi/mi-cmds.h | 1 +
> gdb/record-btrace.c | 12 +++
> gdb/target-delegates.c | 27 ++++++
> gdb/target.c | 8 ++
> gdb/target.h | 7 ++
> .../gdb.mi/mi-function_call_history.c | 43 +++++++++
> .../gdb.mi/mi-function_call_history.exp | 89 +++++++++++++++++++
> 12 files changed, 279 insertions(+)
> create mode 100644 gdb/mi/mi-cmd-record.c
> create mode 100644 gdb/mi/mi-cmd-record.h
> create mode 100644 gdb/testsuite/gdb.mi/mi-function_call_history.c
> create mode 100644 gdb/testsuite/gdb.mi/mi-function_call_history.exp
Thanks, the documentation part is OK.
next prev parent reply other threads:[~2022-07-06 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 13:36 [PATCH v3 0/2] Function call history patches (MI) Ari Hannula
2022-07-06 13:36 ` [PATCH v3 1/2] [func_call] Add function-call-history-length command to MI Ari Hannula
2022-07-06 13:45 ` Eli Zaretskii [this message]
2022-07-06 13:36 ` [PATCH v3 2/2] [func_call] Add function-call-history " Ari Hannula
2022-07-06 13:51 ` Eli Zaretskii
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=83bku273t7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ari.hannula@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tim.wiederhake@intel.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).