On Thu, May 22, 2008 at 08:23:27PM +0530, S h i v wrote: > Are there any conditions under which it provides the details. In my > case the entries where as below(provided for one of the functions): > ------------------------------------------------------------------------------------ > 84452 pid763 a.out foo return > > Probe Description Attributes > Identifier Names: Private > Data Semantics: Private > Dependency Class: Unknown > > Argument Attributes > Identifier Names: Private > Data Semantics: Private > Dependency Class: Unknown > > Argument Types > None > ------------------------------------------------------------------------------------ > > I ran this test with the functions in a different libraries(assuming > the .so file might export some information) - a.out linking to > libexternal.so where the .so file had the functions implemented. > Result was no different. > I will keep a lookout for alternatives.
Arguments for fbt probes, for example, are derived from CTF data that's compiled into the kernel. While Solaris libraries are compiled with CTF data, DTrace doesn't yet include that information in its probes. For the moment, you'll have to determine the type of arguments by hand and use the argN variables casting them as appropriate and bearing in mind potential bitness differences between applications and the kernel. I hope that helps. Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
