dtrace discuss - Jun 2007 - dtrace script generates output in older S10 but not recent S10 or S11

Hi,

I have a dtrace script that generates lots of output with Solaris 10 from a year
ago,
but fails to generate anything with recent versions of Solaris 10 & 11.
I''m wondering
if there was some change in dtrace usage or could this be a bug? Any help would 
be most appreciated.

Below ia the script, how to test it, and which Solaris versions succeeded
and which ones failed to generate any output.

Regards,
Miriam Blatt

---------------------------------------------------------
Here is the script tracecalls.d :

#!/usr/sbin/dtrace -ws
#pragma D option flowindent

BEGIN
{
       self->traceme = 0;
}

pid$target::main:entry
{
       self -> traceme = 1;
}

pid$target::main:return
{
       self -> traceme = 0;
}
pid$target:::entry
/self->traceme/
{
}

pid$target:::return
/self->traceme/
{
}

-----------------------------------------------------------
The script was tested as follows:

  sudo dtrace -s tracecalls.d -c "sleep 60"

---------------------------------------------------------------------------------
Generates lots of output on this OS:
        Solaris 10 6/06 s10s_u2wos_07a SPARC -  Assembled 19 April 2006

Fails to generate anything on these OSes:
          Solaris 10 7/07 s10s_u4wos_09 SPARC  -  Assembled 05 June 2007
          Solaris Nevada snv_61 SPARC               -  Assembled 26 March 2007
--
This message posted from opensolaris.org

Hi Miriam,

You''re hitting the following bug:

  6535590 Pid provider doesn''t work with probe "main:entry"

It should be available in the latest SX build of Solaris Nevada and it will
be included in a future S10 update. Sorry about that.

Adam

On Thu, Jun 28, 2007 at 05:47:54PM -0700, Miriam Blatt
wrote:
> Hi,
> 
> I have a dtrace script that generates lots of output with Solaris 10 from a
year ago,
> but fails to generate anything with recent versions of Solaris 10 & 11.
I''m wondering
> if there was some change in dtrace usage or could this be a bug? Any help
would
> be most appreciated.
> 
> Below ia the script, how to test it, and which Solaris versions succeeded
> and which ones failed to generate any output.
> 
> Regards,
> Miriam Blatt
> 
> ---------------------------------------------------------
> Here is the script tracecalls.d :
> 
> #!/usr/sbin/dtrace -ws
> #pragma D option flowindent
> 
> BEGIN
> {
>        self->traceme = 0;
> }
> 
> pid$target::main:entry
> {
>        self -> traceme = 1;
> }
> 
> pid$target::main:return
> {
>        self -> traceme = 0;
> }
> pid$target:::entry
> /self->traceme/
> {
> }
> 
> pid$target:::return
> /self->traceme/
> {
> }
> 
> -----------------------------------------------------------
> The script was tested as follows:
> 
>   sudo dtrace -s tracecalls.d -c "sleep 60"
> 
>
---------------------------------------------------------------------------------
> Generates lots of output on this OS:
>         Solaris 10 6/06 s10s_u2wos_07a SPARC -  Assembled 19 April 2006
> 
> Fails to generate anything on these OSes:
>           Solaris 10 7/07 s10s_u4wos_09 SPARC  -  Assembled 05 June 2007
>           Solaris Nevada snv_61 SPARC               -  Assembled 26 March
2007
> --
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl