This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/3] Implement support for SystemTap probes on userspace
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: sergiodj at redhat dot com, gdb-patches at sourceware dot org, tromey at redhat dot com
- Date: Sat, 10 Mar 2012 11:06:16 +0200
- Subject: Re: [PATCH 0/3] Implement support for SystemTap probes on userspace
- References: <m3boo5cyd8.fsf@redhat.com> <83haxwzy92.fsf@gnu.org> <20120310085433.GA26446@host2.jankratochvil.net>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 10 Mar 2012 09:54:33 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Sergio Durigan Junior <sergiodj@redhat.com>, gdb-patches@sourceware.org,
> tromey@redhat.com
>
> > 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.
>
> There can be "info probes stap" and "info probes foo" in the future with "info
> probes" calling all the existing probe backends.
Works for me. Or maybe "info sdt-probes" that would cover all of the
varieties of this kind of probes, as in my other suggestion.
> > > (gdb) b -probe m4
> > > Breakpoint 1 at 0x400505
> >
> > Again, either "break -stap-probe" or even just "break -stap" would be
> > better, IMO.
>
> Again -probe may try to find that probe in all the probe backends, later
> extensible by -probe-stap and -probe-foo?
Could be. Or "break -std-probe", which is general enough to cover
several varieties, and yet less general than just "-probe".
Thanks.