OpenSolaris

Printable Version Enter a New Search
Bug ID 6672627
Synopsis Code optimizer cause problems for dtrace -G
State 10-Fix Delivered (Fix available in build)
Category:Subcategory kernel:dtrace
Keywords
Responsible Engineer Adam Leventhal
Reported Against patch_xx , s10u4_fcs
Duplicate Of
Introduced In
Commit to Fix snv_88
Fixed In snv_88
Release Fixed solaris_nevada(snv_88)
Related Bugs 6589130 , 6784947 , 6855626 , 6858502
Submit Date 7-March-2008
Last Update Date 23-April-2008
Description 
I have added USDT probes to my application, and when I try to compile the source with -xO2 dtrace -G is no longer able to instrument the code. 

It seems to me that the problem is that I try to trigger a dtrace probe as the last statement in my function (if I add an extra statement beneath where I call the probe, the problem disappears). I have attached a small test-case to reproduce the problem.

I have not seen this problem with Sun Studio 11.
[ahl 3.21.2008]

Yes, it appears that the DTrace object file processing is being stymied by the tail-call. This shouldn't be hard to fix.
Work Around 
N/A
Comments 
N/A