This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH V2 3/9] New commands `enable probe' and `disable probe'.
- From: Doug Evans <dje at google dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: "Jose E. Marchesi" <jose dot marchesi at oracle dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Thu, 16 Oct 2014 17:07:05 -0700
- Subject: Re: [PATCH V2 3/9] New commands `enable probe' and `disable probe'.
- Authentication-results: sourceware.org; auth=none
- References: <1412961772-16249-1-git-send-email-jose dot marchesi at oracle dot com> <1412961772-16249-4-git-send-email-jose dot marchesi at oracle dot com> <21560 dot 22449 dot 803178 dot 90104 at ruffy2 dot mtv dot corp dot google dot com> <878uknun2f dot fsf at oracle dot com> <CADPb22Q=OE4M+UbJHXQGR3CY0QXLs6w6ggDBohnaK5MxeMyTZg at mail dot gmail dot com> <8761fmqxul dot fsf at redhat dot com>
On Tue, Oct 14, 2014 at 12:01 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Monday, October 13 2014, Doug Evans wrote:
>
>> On Fri, Oct 10, 2014 at 11:39 PM, Jose E. Marchesi
>> <jose.marchesi@oracle.com> wrote:
>>>
>>> Hi Doug.
>>>
>>> Would it be useful to have "info probes" show
>>> the enable/disable state of each probe?
>>> Or at least know which ones have been disabled.
>>>
>>> Right, `info probes' actually tells you the "Enabled" status of the
>>> probes, provided there is at least one dtrace probe in the executable.
>>> For example:
>>>
>>> (gdb) info probes
>>> Provider Name Where Semaphore Enabled Object
>>> demo am-main 0x0000000000400c96 n/a /home/jemarch/oracle/usdt/demo
>>> demo another 0x0000000000400c8b n/a always /home/jemarch/oracle/usdt/demo
>>> demo progress-counter 0x0000000000400c81 n/a no /home/jemarch/oracle/usdt/demo
>>
>> Thanks. I couldn't find it, where should I look?
>
> This is on patch 1/9.
Thanks.
I found the details of the "Enabled" column in 5/9.