From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [PATCH 0/3] Implement support for SystemTap probes on userspace
Date: Sat, 10 Mar 2012 15:52:00 -0000 [thread overview]
Message-ID: <m3zkboa1y9.fsf@redhat.com> (raw)
In-Reply-To: <83eht0zuyf.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 10 Mar 2012 11:06:16 +0200")
On Saturday, March 10 2012, Eli Zaretskii wrote:
>> 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.
I don't really have a preference (though I lean towards Jan suggestion
because of how GDB already deals with such cases). So, which one do you
guys prefer?
--
Sergio
next prev parent reply other threads:[~2012-03-10 15:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 20:29 Sergio Durigan Junior
2012-03-09 20:32 ` [PATCH 1/3] Refactor internal variable mechanism Sergio Durigan Junior
2012-03-09 21:03 ` Tom Tromey
2012-03-10 4:02 ` Sergio Durigan Junior
2012-03-09 20:34 ` [PATCH 3/3] Use longjmp and exception probes when available Sergio Durigan Junior
2012-03-09 20:34 ` [PATCH 2/3] Implement new features needed for handling SystemTap probes Sergio Durigan Junior
2012-03-10 8:38 ` Eli Zaretskii
2012-03-10 16:56 ` Mark Kettenis
2012-03-12 15:11 ` Tom Tromey
2012-03-13 8:58 ` Mark Kettenis
2012-03-13 16:06 ` Sergio Durigan Junior
2012-03-15 20:44 ` Tom Tromey
2012-03-16 14:52 ` Mark Kettenis
2012-03-16 18:17 ` Tom Tromey
2012-03-10 19:22 ` Jan Kratochvil
2012-03-12 20:37 ` Tom Tromey
2012-03-12 23:15 ` Jan Kratochvil
2012-03-15 15:40 ` Pedro Alves
2012-03-15 15:36 ` Pedro Alves
2012-03-15 20:50 ` Tom Tromey
2012-03-09 21:15 ` [PATCH 0/3] Implement support for SystemTap probes on userspace Tom Tromey
2012-03-10 3:51 ` Sergio Durigan Junior
2012-03-10 7:55 ` Eli Zaretskii
2012-03-10 8:55 ` Jan Kratochvil
2012-03-10 9:06 ` Eli Zaretskii
2012-03-10 15:52 ` Sergio Durigan Junior [this message]
2012-03-12 19:59 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zkboa1y9.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox