public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: Stan Cox <scox@redhat.com>, systemtap@sourceware.org
Subject: Re: new static user probe types
Date: Thu, 23 Jul 2009 19:33:00 -0000	[thread overview]
Message-ID: <20090723193338.23C681C7@magilla.sf.frob.com> (raw)
In-Reply-To: Mark Wielaard's message of  Thursday, 23 July 2009 12:28:36 +0200 <1248344916.3494.33.camel@springer.wildebeest.org>

> The .probes section stores the addresses of the generated labels that
> are used to find the probe addresses. This isn't a problem for an
> executable that isn't relocatable. But it is for shared libraries which
> has relocatable addresses (if you have selinux memory protection turned
> on). In that case the section has to be writable for the linker. See
> http://sourceware.org/bugzilla/show_bug.cgi?id=10381

Bah!  I'm sure I already told you about doing this right!  The .probes
section should contain relative addresses fixed at compile time, just like
every other kind of static annotation (and code itself) is made PIC-friendly.

      parent reply	other threads:[~2009-07-23 19:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 21:26 Stan Cox
2009-07-15 16:19 ` Stan Cox
2009-07-15 18:39   ` Josh Stone
2009-07-15 20:47     ` Stan Cox
2009-07-15 21:57       ` Josh Stone
2009-07-16 13:44         ` Stan Cox
2009-07-20 18:34   ` Stan Cox
2009-07-22 10:42     ` Mark Wielaard
2009-07-22 14:39       ` Frank Ch. Eigler
2009-07-22 17:10         ` Mark Wielaard
2009-07-29 15:44           ` Stan Cox
2009-07-29 15:51             ` Stan Cox
2009-07-23  3:07       ` Roland McGrath
2009-07-23 10:28         ` Mark Wielaard
2009-07-23 14:40           ` Frank Ch. Eigler
2009-07-23 19:33           ` Roland McGrath [this message]

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=20090723193338.23C681C7@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=mjw@redhat.com \
    --cc=scox@redhat.com \
    --cc=systemtap@sourceware.org \
    /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).