[Bug cli/27159] maintenance command to ignore probes

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=27159

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=08c59458a106038c6d678621e7290948127671e2

commit 08c59458a106038c6d678621e7290948127671e2
Author: Tom de Vries <tdevries@suse.de>
Date:   Sat Dec 31 10:23:06 2022 +0100

    [gdb/cli] Add maintenance ignore-probes

    There's a command "disable probes", but SystemTap probes, for instance
    libc:longjmp cannot be disabled:
    ...
    $ gdb -q -batch a.out -ex start -ex "disable probes libc ^longjmp$"
      ...
    Probe libc:longjmp cannot be disabled.
    Probe libc:longjmp cannot be disabled.
    Probe libc:longjmp cannot be disabled.
    ...

    Add a command "maintenance ignore-probes" that ignores probes during
    get_probes, such that we can easily pretend to use a libc without the
    libc:longjmp probe:
    ...
    (gdb) maint ignore-probes -verbose libc ^longjmp$
    ignore-probes filter has been set to:
    PROVIDER: 'libc'
    PROBE_NAME: '^longjmp$'
    OBJNAME: ''
    (gdb) start ^M
      ...
    Ignoring SystemTap probe libc longjmp in /lib64/libc.so.6.^M
    Ignoring SystemTap probe libc longjmp in /lib64/libc.so.6.^M
    Ignoring SystemTap probe libc longjmp in /lib64/libc.so.6.^M
    ...

    The "Ignoring ..." messages can be suppressed by not using -verbose.

    Note that as with "disable probes", running simply "maint ignore-probes"
    ignores all probes.

    The ignore-probes filter can be reset by using:
    ...
    (gdb) maint ignore-probes -reset
    ignore-probes filter has been reset
    ...

    For now, the command is only supported for SystemTap probes.

    PR cli/27159
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27159

-- 
You are receiving this mail because:
You are on the CC list for the bug.