[dtrace-discuss] Re: Chime and #includes -

[Tom Erickson]

At first I thought the answer was simple: specify the "cpp" option in the Chime display description. Unfortunately it doesn't work because Chime reads the contents of a program file into a string buffer then asks DTrace to compile the program as a string. I didn't realize that the DTrace library ignores the "cpp" option when compiling a program string rather than a program file. I started treating program file contents as strings when I added program placeholders (like macro variables, but replaced by Chime rather than DTrace).

I'm sorry, I should have answered this much sooner, but didn't see it in my email. I'll let you know as soon as there is a fix or a work-around for this issue.

Thanks,

Tom
 
 
This message posted from opensolaris.org