From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Modify stap-probe.h to identify SystemTap probes
Date: Sat, 05 May 2012 07:05:00 -0000 [thread overview]
Message-ID: <m3havvqfaf.fsf@redhat.com> (raw)
In-Reply-To: <20120505065253.GA8272@host2.jankratochvil.net> (Jan Kratochvil's message of "Sat, 5 May 2012 08:52:53 +0200")
On Saturday, May 05 2012, Jan Kratochvil wrote:
> On Sat, 05 May 2012 08:41:49 +0200, Sergio Durigan Junior wrote:
>> On Saturday, May 05 2012, Jan Kratochvil wrote:
>> > If the current probe.h interface is insufficient then it should be extended.
>>
>> I agree, but that's not the case. `probe.h' is sufficient, but it is
>> not its responsibility to tell if a probe foo is a SystemTap probe.
>
> Why cannot probe XYZ serve the task a SystemTap probe does? The name
> "SystemTap" makes the probe somehow unique no other probe kind can be placed
> at the same address providing the same information?
Currently only SystemTap is implemented, and SystemTap userspace probes
can have arguments, but this may not be true for all types of probes
that will eventually be implemented. Also, and maybe most important,
only SystemTap probes are used inside glibc/libgcc for this purpose, so
allowing any probe type to be accepted in this case is not conceptually
right IMO.
If any other probe of any other type is included in glibc/libgcc for the
same purpose, it is easy to allow this type of probe in the code too.
--
Sergio
next prev parent reply other threads:[~2012-05-05 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120504152129.GA7418@redhat.com>
[not found] ` <m37gwrs0m6.fsf@redhat.com>
[not found] ` <20120505060312.GA7019@host2.jankratochvil.net>
[not found] ` <m3vckbqhsg.fsf@redhat.com>
[not found] ` <20120505062315.GA7458@host2.jankratochvil.net>
2012-05-05 6:42 ` Sergio Durigan Junior
2012-05-05 6:53 ` Jan Kratochvil
2012-05-05 7:05 ` Sergio Durigan Junior [this message]
2012-05-05 7:12 ` Jan Kratochvil
2012-05-05 7:21 ` Sergio Durigan Junior
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=m3havvqfaf.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).