From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-88746-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 10800 invoked by alias); 10 Mar 2012 07:55:20 -0000
Received: (qmail 10789 invoked by uid 22791); 10 Mar 2012 07:55:18 -0000
X-SWARE-Spam-Status: No, hits=-1.1 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 10 Mar 2012 07:55:01 +0000
Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M0N00C00SIVLF00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Sat, 10 Mar 2012 09:54:58 +0200 (IST)
Received: from HOME-C4E4A596F7 ([84.229.138.42]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M0N00CUHSNLLM00@a-mtaout22.012.net.il>; Sat, 10 Mar 2012 09:54:58 +0200 (IST)
Date: Sat, 10 Mar 2012 07:55:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH 0/3] Implement support for SystemTap probes on userspace
In-reply-to: <m3boo5cyd8.fsf@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83haxwzy92.fsf@gnu.org>
References: <m3boo5cyd8.fsf@redhat.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2012-03/txt/msg00368.txt.bz2

> 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.