From: Ari Hannula <ari.hannula@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] Functions call history patches
Date: Thu, 10 Feb 2022 14:52:38 +0100 [thread overview]
Message-ID: <20220210135243.3127629-1-ari.hannula@intel.com> (raw)
Hi all,
On behalf of Tim and Ravi, who no longer work at Intel, I am posting these patches
for review. They make some fixes to function call history tests and add new MI commands
to access the function call history, including tests.
Regards,
Ari
Tim Wiederhake (4):
[func_call] Add possible spelling of linker error message.
[func_call] Fix MI output for function call history.
[func_call] Add function-call-history-length command to MI.
[func_call] Add function-call-history command to MI.
ravitheja.addepally (1):
[func_call] New tests for a btrace crash.
gdb/mi/mi-cmds.c | 13 +-
gdb/mi/mi-cmds.h | 2 +
gdb/record-btrace.c | 38 +++-
gdb/record.c | 61 ++++++
gdb/record.h | 11 ++
gdb/target-delegates.c | 23 +++
gdb/target.c | 8 +
gdb/target.h | 7 +
...rver-multithreaded-function-call-history.c | 70 +++++++
...er-multithreaded-function-call-history.exp | 61 ++++++
.../gdb.mi/mi-function_call_history.c | 43 ++++
.../gdb.mi/mi-function_call_history.exp | 183 ++++++++++++++++++
gdb/testsuite/lib/gdb.exp | 3 +
13 files changed, 513 insertions(+), 10 deletions(-)
create mode 100644 gdb/testsuite/gdb.btrace/server-multithreaded-function-call-history.c
create mode 100644 gdb/testsuite/gdb.btrace/server-multithreaded-function-call-history.exp
create mode 100644 gdb/testsuite/gdb.mi/mi-function_call_history.c
create mode 100644 gdb/testsuite/gdb.mi/mi-function_call_history.exp
--
2.25.1
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2022-02-10 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:52 Ari Hannula [this message]
2022-02-10 13:52 ` [PATCH 1/5] [func_call] Add possible spelling of linker error message Ari Hannula
2022-03-17 17:58 ` Metzger, Markus T
2022-03-17 18:45 ` Keith Seitz
2022-02-10 13:52 ` [PATCH 2/5] [func_call] New tests for a btrace crash Ari Hannula
2022-03-17 17:58 ` Metzger, Markus T
2022-02-10 13:52 ` [PATCH 3/5] [func_call] Fix MI output for function call history Ari Hannula
2022-03-17 17:58 ` Metzger, Markus T
2022-02-10 13:52 ` [PATCH 4/5] [func_call] Add function-call-history-length command to MI Ari Hannula
2022-03-17 17:59 ` Metzger, Markus T
2022-02-10 13:52 ` [PATCH 5/5] [func_call] Add function-call-history " Ari Hannula
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=20220210135243.3127629-1-ari.hannula@intel.com \
--to=ari.hannula@intel.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).