[dtrace-discuss] Fwd: DTrace bug with 6 parameters to C++ function containing multiple DTrace probe entries

[Mikael Ronström]

Hi,
Had to forward to another email box to be able to send it :(

>
>
> Hi,
> I don't know how to file bugs towards DTrace yet, but here seems to  
> be one anyways.
> I made a DTrace probe that was part of an inline function, this  
> inline function was
> called in numberous places. However one of those places seems to  
> cause special pain.
>
> The function contained 6 parameters and DTrace's name of it was
> Undefined                       first referenced
>  symbol                             in file
> _ZN4Dbtc20deleteFromIndexTableEP6SignalPNS_18TcFiredTriggerDataEP3PtrI 
> NS_16ApiConnectRecordEEPS4_INS_15TcConnectRecordEEPNS_11T blocks/ 
> ndb_blocks_dtrace.o
>  The function looked like this:
>   void deleteFromIndexTable(Signal* signal,
>                             TcFiredTriggerData* firedTriggerData,
>                             ApiConnectRecordPtr* transPtr,
>                             TcConnectRecordPtr* opPtr,
>                             TcIndexData* indexData,
>                             bool holdOperation = false);
>
> From what I can see this is a simple matter of an array being  
> declared to short in DTrace since it seems to
> cut the name short here.
>
> The workaround is of course to get rid of a few parameters in some  
> way and this works, going down to
> four parameters and it works fine. However it's a similar function  
> where this works so is properly a bit
more complex.
>
>
> Rgrds Mikael
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20080516/f2e3ab11/attachment.html