This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: rethinking syscall tapset


On Wed, 2006-02-08 at 14:00 -0500, Frank Ch. Eigler wrote:
> Hi -
> 
> > > > Also, I am planning to eventually make returnp indicate something
> > > > about the return value's type.
> > > Why, considering our static typing?
> > How would that work with return values?
> 
> Normal functions' return values are put through the type
> check/inference engine the same way as other variables, so that's the
> basic model.  Do you believe the users of .return probe values (say,
> open() rc and/or errno) need some sort of type polymorphism?  Can you
> provide a script scenario where a run-time type-code conditional is
> needed?

Sure.

probe syscall.*.return {
    printf("%d\n", returnval())
}

How do I know that the returnvalue is not an address and should be
printed in hex?



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]