From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: sergiodj@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Implement new features needed for handling SystemTap probes
Date: Thu, 15 Mar 2012 20:44:00 -0000 [thread overview]
Message-ID: <87ipi5y4qt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201203130858.q2D8w5fe030670@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Tue, 13 Mar 2012 09:58:05 +0100 (CET)")
>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
Tom> sdt.h is really more like an ELF feature.
Mark> Can you elaborate on that? I've googled around a bit but didn't
Mark> really find anything that describes how SystemTap works; only stuff
Mark> that describes how great it is and how it can be used. I did notice
Mark> that DTrace uses a header file with that name as well, but it seems
Mark> that the interfaces defined in the DTrace sdt.h are completely
Mark> different from the SystemTap one.
Yeah, sorry. That was too brief.
The static probes in this case are intended to be source- (but not
binary-) compatible with DTrace. They are implemented entirely in a
header file (technically two headers but one is of the "config.h"
variety) and assume ELF and GCC.
The header is independent of SystemTap proper; it just came from the
SystemTap project and so it is maintained in that source repository.
There's been some talk that it will be used as the basis for UST markers
as well, but AFAIK this work hasn't happened yet.
I don't know of any barrier to this header working as-is on other
ELF+GCC platforms. I haven't tried it myself.
If you still want this in the Linux tdep files, I suppose it can be
done.
Tom
next prev parent reply other threads:[~2012-03-15 20:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 20:29 [PATCH 0/3] Implement support for SystemTap probes on userspace 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 [this message]
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
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=87ipi5y4qt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=sergiodj@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