From: Tim Wiederhake <tim.wiederhake@intel.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com, markus.t.metzger@intel.com
Subject: [PATCH v3 4/8] Add record_start function.
Date: Mon, 21 Nov 2016 15:49:00 -0000 [thread overview]
Message-ID: <1479743318-24523-5-git-send-email-tim.wiederhake@intel.com> (raw)
In-Reply-To: <1479743318-24523-1-git-send-email-tim.wiederhake@intel.com>
2016-11-21 Tim Wiederhake <tim.wiederhake@intel.com>
gdb/ChangeLog
* record.h (record_start): New export.
* record.c (record_start): New function.
---
gdb/record.c | 28 ++++++++++++++++++++++++++++
gdb/record.h | 5 +++++
2 files changed, 33 insertions(+)
diff --git a/gdb/record.c b/gdb/record.c
index 34ebd1b..6df8ba1 100644
--- a/gdb/record.c
+++ b/gdb/record.c
@@ -93,6 +93,34 @@ record_preopen (void)
/* See record.h. */
+void
+record_start (const char *method, const char *format, int from_tty)
+{
+ if (method == NULL)
+ {
+ if (format == NULL)
+ return execute_command ("record", from_tty);
+ }
+ else if (strcmp (method, "full") == 0)
+ {
+ if (format == NULL)
+ return execute_command ("record full", from_tty);
+ }
+ else if (strcmp (method, "btrace") == 0)
+ {
+ if (format == NULL)
+ return execute_command ("record btrace", from_tty);
+ if (strcmp (format, "bts") == 0)
+ return execute_command ("record btrace bts", from_tty);
+ if (strcmp (format, "pt") == 0)
+ return execute_command ("record btrace pt", from_tty);
+ }
+
+ error (_("Invalid argument."));
+}
+
+/* See record.h. */
+
int
record_read_memory (struct gdbarch *gdbarch,
CORE_ADDR memaddr, gdb_byte *myaddr,
diff --git a/gdb/record.h b/gdb/record.h
index 84440c64..eb091ce 100644
--- a/gdb/record.h
+++ b/gdb/record.h
@@ -91,4 +91,9 @@ extern struct target_ops *find_record_target (void);
it does anything. */
extern void record_preopen (void);
+/* Internal function that starts recording with the given METHOD and FORMAT.
+ NULL means default method or format. */
+extern void record_start (const char *method, const char *format,
+ int from_tty);
+
#endif /* _RECORD_H_ */
--
2.7.4
next prev parent reply other threads:[~2016-11-21 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 15:49 [PATCH v3 0/8] Python bindings for btrace recordings Tim Wiederhake
2016-11-21 15:49 ` [PATCH v3 8/8] Add documentation for new instruction record Python bindings Tim Wiederhake
2016-11-29 15:48 ` Metzger, Markus T
2016-11-29 17:32 ` Eli Zaretskii
2016-11-21 15:49 ` [PATCH v3 6/8] python: Implement btrace Python bindings for record history Tim Wiederhake
2016-11-29 15:48 ` Metzger, Markus T
2016-11-21 15:49 ` [PATCH v3 2/8] btrace: Export btrace_decode_error function Tim Wiederhake
2016-11-29 15:47 ` Metzger, Markus T
2016-11-21 15:49 ` Tim Wiederhake [this message]
2016-11-29 15:47 ` [PATCH v3 4/8] Add record_start function Metzger, Markus T
2016-11-21 15:49 ` [PATCH v3 7/8] python: Add tests for record Python bindings Tim Wiederhake
2016-11-29 15:48 ` Metzger, Markus T
2016-11-21 15:49 ` [PATCH v3 1/8] btrace: Count gaps as one instruction explicitly Tim Wiederhake
2016-11-29 15:47 ` Metzger, Markus T
2016-11-21 15:49 ` [PATCH v3 5/8] python: Create Python bindings for record history Tim Wiederhake
2016-11-29 15:48 ` Metzger, Markus T
2016-11-21 15:49 ` [PATCH v3 3/8] btrace: Use binary search to find instruction Tim Wiederhake
2016-11-29 15:47 ` Metzger, Markus T
2016-11-29 15:49 ` [PATCH v3 0/8] Python bindings for btrace recordings Metzger, Markus T
2016-11-30 23:50 [PATCH v3 4/8] Add record_start function Doug Evans
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=1479743318-24523-5-git-send-email-tim.wiederhake@intel.com \
--to=tim.wiederhake@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.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