dtrace discuss - Jul 2006 - RFE for dtrace -h command

I am working on a software system for multiple platforms, and I would like to
add dtrace probes to my application. I would like to avoid to write:

#ifdef HAVE_DTRACE
   FOO_BAR(a);
#endif

each time I fire a dtrace probe. I would also like to avoid to edit the file
generated by dtrace -h each time I regenerate the file, so it would be nice if
the dtrace -h command also created empty macros protected by some preprocessor
symbol.

(i would also prefer if all of the macros had a DTRACE_ prefix so that it would
be clear for everyone the purpose of the statement, but that''s probably
just me :-))

Trond
 
 
This message posted from opensolaris.org

Hi Trond,

This might be a good extension to this RFE:

  http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6432394

Adam

On Tue, Jul 25, 2006 at 01:03:50AM -0700, Trond Norbye
wrote:
> I am working on a software system for multiple platforms, and I would like
to add dtrace probes to my application. I would like to avoid to write:
> 
> #ifdef HAVE_DTRACE
>    FOO_BAR(a);
> #endif
> 
> each time I fire a dtrace probe. I would also like to avoid to edit the
file generated by dtrace -h each time I regenerate the file, so it would be nice
if the dtrace -h command also created empty macros protected by some
preprocessor symbol.
> 
> (i would also prefer if all of the macros had a DTRACE_ prefix so that it
would be clear for everyone the purpose of the statement, but that''s
probably just me :-))
> 
> Trond
>  
>  
> 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