RE: Anyone tried SystemTap with the latest RHEL5 Beta refresh

["Nguyen, Thang P" <thang dot p dot nguyen at intel dot com>]

For example:

> stap ioblock_script.stp

------ ioblock_script.stp ----
#! stap

probe begin {
  printf("DEVNAME\tSECTOR\tRW\n")
}
probe ioblock.request {
   printf("%s\t%d\t%s\n", devname, sector, bio_rw_str(rw))
}
probe ioblock.end {
   printf("%s\t%d\t%s\n", devname, sector, bio_rw_str(rw))
}

Thang

>-----Original Message-----
>From: systemtap-owner@sourceware.org [mailto:systemtap-
>owner@sourceware.org] On Behalf Of Mike Mason
>Sent: Thursday, October 26, 2006 1:39 PM
>To: Vara Prasad
>Cc: William Cohen; SystemTAP
>Subject: Re: Anyone tried SystemTap with the latest RHEL5 Beta refresh
>
>Looks like he's trying to run the ioblock tapset file directly?  That
won't
>work.  Stap ends up loading ioblock.stp twice which results in the
>duplicate probe errors. He needs to write a script that uses the
ioblock
>tapset probes.
>
>- Mike
>
>Vara Prasad wrote:
>> One of my colleague tried SystemTap on x86_64 machine got the
following
>> error
>> stap -g ioblock.stp
>> while: registering probe alias ioblock.submit =
>> kernel.function("submit_bio")
>> semantic error: duplicate probe point pattern
>> while: registering probe alias ioblock.end =
kernel.function("bio_endio")
>> semantic error: duplicate probe point pattern
>> Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
>>
>>
>> I dont have the setup to debug his problem, was wondering if anyone
has
>> experienced these problems.
>> He is using stock RHEL 5 setup. I thought we now bundle everything
>> needed in RHEL5, correct.
>> Does he needs to download any additional packages?
>>
>> Thanks for your help,
>> Vara Prasad
>>