From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5945 invoked by alias); 13 Mar 2012 08:58:28 -0000 Received: (qmail 5936 invoked by uid 22791); 13 Mar 2012 08:58:27 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Mar 2012 08:58:12 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3) with ESMTP id q2D8w7D0008510; Tue, 13 Mar 2012 09:58:07 +0100 (CET) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3/Submit) id q2D8w5fe030670; Tue, 13 Mar 2012 09:58:05 +0100 (CET) Date: Tue, 13 Mar 2012 08:58:00 -0000 Message-Id: <201203130858.q2D8w5fe030670@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: tromey@redhat.com CC: sergiodj@redhat.com, gdb-patches@sourceware.org In-reply-to: <87wr6pq4s3.fsf@fleche.redhat.com> (message from Tom Tromey on Mon, 12 Mar 2012 08:21:00 -0600) 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> 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/msg00427.txt.bz2 > From: Tom Tromey > Date: Mon, 12 Mar 2012 08:21:00 -0600 > > >>>>> "Mark" == Mark Kettenis writes: > > Mark> As far as I can tell SystemTap is Linux-specific. So I'd think its > Mark> support should go completely in Linux-specific -tdep.c files. > > sdt.h is really more like an ELF feature. Can you elaborate on that? I've googled around a bit but didn't really find anything that describes how SystemTap works; only stuff that describes how great it is and how it can be used. I did notice that DTrace uses a header file with that name as well, but it seems that the interfaces defined in the DTrace sdt.h are completely different from the SystemTap one. All evidence I have points towards the functions in i386-tdep.c being SystemTap-specific; that's probably why they have "stap" in their name ;). They're only used from i386-linux-tdep.c, so it makes much more sense to put them there. If somebody ever ports (or reimplements) SystemTap for another OS, we can always move them. The same thing holds for arm-tdep.c vs. arm-linux-tdep.c of course.