Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: Tom Tromey <tromey@redhat.com>,
	"Cui, Dexuan" <dexuan.cui@intel.com>,
	       ltt-dev <ltt-dev@lists.casi.polymtl.ca>,
	gdb <gdb@sourceware.org>,
	       systemtap@sources.redhat.com
Subject: Re: [ltt-dev] gdb-7.2 can't build with lttng-ust-0.12
Date: Wed, 27 Apr 2011 00:26:00 -0000	[thread overview]
Message-ID: <4DB762B9.70505@redhat.com> (raw)
In-Reply-To: <BLU0-SMTP3759F7830D97C89E9BCE9796990@phx.gbl>

On 04/26/2011 02:41 PM, Mathieu Desnoyers wrote:
> Yes, the goal is to rely on sdt.h as soon as it supports a e.g.
> STAP_PROBEV (with variable number of args). The Josh Stone found a neat
> trick to do it, and I think he is preparing an updated version.

I committed STAP_PROBEV to systemtap.git a couple of weeks ago.  We just
haven't prepared a new release yet.  (soon...)

> The only concern here is the packaging: if we depend on sdt.h, we have
> to either ship it with UST, or have one more dependency on a package
> available for all architectures that only contain this header. Thoughts ?

In Fedora and RHEL, systemtap-sdt-devel.rpm contains the sdt.h header
and a "dtrace" python script.  The latter is only needed for projects
that are specifically building the DTrace way.  Distros that don't care
about that could get away with packaging just the header.

As for "all" architectures, there's very little arch-specific code in
sdt.h, currently contained in two defines.  There's _SDT_NOP for
choosing the variation of "nop" of "nop 0", and there's _SDT_ARGTMPL to
provide a special template for the powerpc case.  If other archs need
special consideration, we'll gladly accept patches.

Josh


  parent reply	other threads:[~2011-04-27  0:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1865303E0DED764181A9D882DEF65FB6931C75A5AA@shsmsx502.ccr.corp.intel.com>
     [not found] ` <BLU0-SMTP7051C411EF9E3864329F4596960@phx.gbl>
2011-04-26  1:51   ` Cui, Dexuan
2011-04-26 18:47     ` Tom Tromey
2011-04-26 21:42       ` Mathieu Desnoyers
     [not found]       ` <BLU0-SMTP3759F7830D97C89E9BCE9796990@phx.gbl>
2011-04-27  0:26         ` Josh Stone [this message]
     [not found]       ` <BLU0-SMTP45CC9DEEE33FD5A526EB3896990@phx.gbl>
2011-04-27 14:32         ` 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=4DB762B9.70505@redhat.com \
    --to=jistone@redhat.com \
    --cc=compudj@krystal.dyndns.org \
    --cc=dexuan.cui@intel.com \
    --cc=gdb@sourceware.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=systemtap@sources.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