[PATCH 0/3] Implement support for SystemTap probes on userspace
Eli Zaretskii
eliz@gnu.org
Sat Mar 10 07:55:00 GMT 2012
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: Tom Tromey <tromey@redhat.com>
> Date: Fri, 09 Mar 2012 17:28:51 -0300
>
> After a long time reworking the patches, I am finally resubmitting them
> for review and, hopefully, inclusion.
Thanks!
> When you start a patched GDB debugging a binary which contains probes in
> it, you can get a list of the probes by using the new `info probes'
> command:
>
> sergio@psique ~/work/src/git/stap-patches/build-64/gdb $ ./gdb -q /tmp/stap-example
> (gdb) info probes
> Provider Name Where Semaphore Object
> teste m4 0x0000000000400505 0x00000000006009f8 /tmp/stap-example
> teste ps 0x00000000004004cd 0x00000000006009fc /tmp/stap-example
> teste two 0x0000000000400484 0x00000000006009f6 /tmp/stap-example
> teste two 0x0000000000400497 0x00000000006009f6 /tmp/stap-example
> teste user 0x00000000004004ad 0x00000000006009f4 /tmp/stap-example
May I suggest that the new command be called "info stap-probes"
instead? IMO, "probe" is much too general, and may conflict in the
future with some other feature that uses similar facilities or
terminology.
> As you can see above, there are 5 probes in the binary. We can now ask
> GDB to put a breakpoint in a probe, by using the new option `-p' or
> `-probe' in the `break' command:
>
> (gdb) b -probe m4
> Breakpoint 1 at 0x400505
Again, either "break -stap-probe" or even just "break -stap" would be
better, IMO.
More information about the Gdb-patches
mailing list