From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [RFC] [gdb/cli] Add maintenance ignore-probes
Date: Tue, 13 Dec 2022 08:58:41 -0700 [thread overview]
Message-ID: <874jtzfg7i.fsf@tromey.com> (raw)
In-Reply-To: <20221207090020.15890-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Wed, 7 Dec 2022 10:00:20 +0100")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> There's a command "disable probes", but SystemTap probes cannot be disabled.
Tom> Add a command "maintenance ignore-probes" that ignores probes during
Tom> get_probes, such that we can easily pretend to use a glibc without say,
Tom> the longjmp probe:
The idea seems sound to me.
Tom> Note that as with "disable probes", running "maint ignore-probes" without
Tom> arguments ignores all probes.
I didn't know about "disable probes" but I see now it's a DTrace thing.
Tom> +/* Implementation of the `maintenance ignore-probes' command. */
Tom> +
Tom> +static void
Tom> +ignore_probes_command (const char *arg, int from_tty)
Tom> +{
Tom> + std::string ignore_provider, ignore_probe_name, ignore_objname;
Tom> +
Tom> + parse_probe_linespec ((const char *) arg, &ignore_provider,
Tom> + &ignore_probe_name, &ignore_objname);
The cast there isn't needed. I'm going to remove the other casts like
this in a second.
Also, maybe if arg==nullptr, this could set ignore_probes_p = false?
That would give a way to undo the change.
Tom> + add_cmd ("ignore-probes", class_maintenance, ignore_probes_command, _("\
Tom> +Ignore probes.\n\
Tom> +Usage: ignore probes [PROVIDER [NAME [OBJECT]]]\n\
Missing the "-" in "ignore-probes".
Tom> +all defined probes. Only supported for SystemTap probes"),
Probably should end with a "."
Tom
next prev parent reply other threads:[~2022-12-13 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 9:00 Tom de Vries via Gdb-patches
2022-12-13 15:58 ` Tom Tromey [this message]
2022-12-13 21:50 ` Tom de Vries via Gdb-patches
2022-12-13 23:39 ` Tom Tromey
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=874jtzfg7i.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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