From: Doug Evans <dje@google.com>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
markus.t.metzger@intel.com
Subject: Re: [PATCH v3 4/8] Add record_start function.
Date: Wed, 30 Nov 2016 23:50:00 -0000 [thread overview]
Message-ID: <94eb2c0b85f889179705428d5ea1@google.com> (raw)
Tim Wiederhake writes:
> 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. */
> +
I'm guessing this is essentially implementing a library API on top of GDB's
CLI.
Yikes. Maybe things will be clearer as I read the rest of the patches.
I'd mention in the function comment that this can throw gdb errors.
> 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 reply other threads:[~2016-11-30 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 23:50 Doug Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-21 15:49 [PATCH v3 0/8] Python bindings for btrace recordings Tim Wiederhake
2016-11-21 15:49 ` [PATCH v3 4/8] Add record_start function Tim Wiederhake
2016-11-29 15:47 ` Metzger, Markus T
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=94eb2c0b85f889179705428d5ea1@google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
--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