This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: _stp_pid no longer there?

From: Martin Hunt <hunt at redhat dot com>
To: Sébastien Dugué <sebastien dot dugue at bull dot net>
Cc: systemtap <systemtap at sources dot redhat dot com>, Pierre PEIFFER <pierre dot peiffer at bull dot net>
Date: Wed, 28 Mar 2007 12:13:26 -0400
Subject: Re: _stp_pid no longer there?
Organization: Red Hat Inc.
References: <20070328120810.37633ce8@frecb000686.frec.bull.fr> <1175093316.6383.6.camel@dragon> <20070328173700.50c48a91@frecb000686.frec.bull.fr>

On Wed, 2007-03-28 at 17:37 +0200, SÃbastien DuguÃ wrote:
> On Wed, 28 Mar 2007 10:48:36 -0400 Martin Hunt <hunt@redhat.com> wrote:

> > The stp_pid() function in context.stp  should work like it used to.
> > 
> 
>   How could it? it just references __stp_pid.
> 
>   just try a:
> 
>     stap -vv -p4 -e 'probe begin {printf("staprun pid %d\n", stp_pid())}'

I meant it would work like normal once I fixed it.

I've checked in the fix for newer kernels with debugfs. For older
kernels I will get the patch in later once I have had a chance to test
it.

Martin

Follow-Ups:
- Re: _stp_pid no longer there?
  - From: Sébastien Dugué

References:
- _stp_pid no longer there?
  - From: Sébastien Dugué
- Re: _stp_pid no longer there?
  - From: Martin Hunt
- Re: _stp_pid no longer there?
  - From: Sébastien Dugué

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]