>> Functions that end in a tail-call to another function can report an >> incorrect return value in the arg1 variable. Take a look at the >> disassembly at the location where you're seeing the apparently >> invalid >> return values to confirm that it's a tail-call. > > Aaah, that exactly happened to me half a year ago, on the same t_* > functions. And I forgot it in the meantime. Would it be sensible to > have > dtrace which would warn you when it detects tail-call optimized > function > ?
It's certainly the case that it's never the right thing to trace arg1 from a tail-call return probe. It would be tricky, but perhaps DTrace could do something to warn against this. I suggest you file a bug. Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
