public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Martin Hunt <hunt@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, systemtap@sourceware.org
Subject: Re: Global constants
Date: Mon, 13 Feb 2006 21:41:00 -0000	[thread overview]
Message-ID: <1139866918.3942.37.camel@monkey2> (raw)
In-Reply-To: <1139863461.11054.51.camel@localhost.localdomain>

On Mon, 2006-02-13 at 20:44 +0000, Mark McLoughlin wrote:
> On Mon, 2006-02-13 at 12:23 -0800, Martin Hunt wrote:
> > On Mon, 2006-02-13 at 20:14 +0000, Mark McLoughlin wrote:
> > 
> > > > something like
> > > > %{ const_O_CREAT = O_CREAT; %}
> > > >   instead of
> > > > O_CREAT = 64
> > > 
> > > 	Absolutely, that was my first thought too ... unfortunately, the kernel
> > > headers don't seem to have all the values e.g. O_ASYNC is only available
> > > as FASYNC ... I didn't take it any further than thinking "uggh, that
> > > sucks", though :-)
> > 
> > I don't understand.
> > 
> > function get_o_creat:long() %{ THIS->__retvalue = O_CREAT; %}
> > 
> > probe begin {
> > 	printf("O_CREAT = %d\n", get_o_creat())
> > }
> > 
> > > stap -g creat.stp
> > O_CREAT = 64
> 
> 	O_CREAT works fine, but try O_ASYNC (AFAIR)

Yeah, a quirk of the kernel headers is that they define FASYNC instead
of the equivalent O_ASYNC. The user headers define both 
# define FASYNC            O_ASYNC

Martin


  reply	other threads:[~2006-02-13 21:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 17:39 Mark McLoughlin
2006-02-13 19:28 ` Frank Ch. Eigler
2006-02-13 19:40   ` Martin Hunt
2006-02-13 20:10     ` Frank Ch. Eigler
2006-02-13 20:20       ` Mark McLoughlin
2006-02-13 20:14     ` Mark McLoughlin
2006-02-13 20:22       ` Martin Hunt
2006-02-13 20:44         ` Mark McLoughlin
2006-02-13 21:41           ` Martin Hunt [this message]
2006-02-14  8:27             ` Mark McLoughlin
2006-02-13 20:09   ` Mark McLoughlin
2006-02-13 20:13 Stone, Joshua I
2006-02-13 20:46 ` Frank Ch. Eigler
2006-02-13 20:36 Stone, Joshua I
2006-02-13 21:05 ` Frank Ch. Eigler
2006-02-13 21:50 Stone, Joshua I
2006-02-13 23:50 ` Frank Ch. Eigler
2006-02-13 22:12 Stone, Joshua I

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=1139866918.3942.37.camel@monkey2 \
    --to=hunt@redhat.com \
    --cc=fche@redhat.com \
    --cc=markmc@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).