From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23778 invoked by alias); 15 Mar 2012 20:44:09 -0000 Received: (qmail 23766 invoked by uid 22791); 15 Mar 2012 20:44:08 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Mar 2012 20:43:40 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q2FKhdkP018664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Mar 2012 16:43:40 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q2FKhc7F020003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 15 Mar 2012 16:43:39 -0400 From: Tom Tromey To: Mark Kettenis Cc: sergiodj@redhat.com, gdb-patches@sourceware.org Subject: Re: [PATCH 2/3] Implement new features needed for handling SystemTap probes References: <201203101655.q2AGte2M019374@glazunov.sibelius.xs4all.nl> <87wr6pq4s3.fsf@fleche.redhat.com> <201203130858.q2D8w5fe030670@glazunov.sibelius.xs4all.nl> Date: Thu, 15 Mar 2012 20:44:00 -0000 In-Reply-To: <201203130858.q2D8w5fe030670@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Tue, 13 Mar 2012 09:58:05 +0100 (CET)") Message-ID: <87ipi5y4qt.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-03/txt/msg00579.txt.bz2 >>>>> "Mark" == Mark Kettenis 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