> OS X's default is to use demangled names. If you add > d -xmangled, you > should be able to match on the mangled names: >
Thanks a lot James. With -xmangled, the function is recognized. But I ran into a new problem, where dtrace says index 2 is out of range for args []! > The args[] array doesn't work with the pid provider, > , you'll need to > use arg0, arg1, etc. Hmm.. DTrace is complaining that 2 is out of range for args[]. arg2 is 64 bit address and it does not have type. So, I can't do things like arg2.m1, etc.. > This isn't doing what you think it is. Pid probes > s are created on > demand, and that isn't > demanding any :-). Its not what you want even if it > did, as a wildcard > will attempt to create all > probes, including offset probes. In other words, > "make a probe for > every instruction in Firefox". > > Its pretty unlikely you'd be able to create enough > h probes before > hitting some kind of memory > limit. This was working and it gave me output (like ustack). Only thing was it did not allow me to use args[] > > Each pid gets its own set of probes. A different pid > d means different > probe ids. Makes sense. :-) > argX is "mostly" the same as args[X]. The difference > e is that argX is > the raw > ABI, not a typed argument. So you'll run into things > like "On this > arch, a 64 bit value > is passed in two argument slots." If you don't get > the answers you > expect, you're probably > going to need to dig into the ABI to figure out where > the data you > want is stored. > > Just in case, here is the document you should hope > e you don't have to > read :-) > > http://developer.apple.com/documentation/DeveloperToo > ls/Conceptual/LowLevelABI/Introduction.html > > James M Is there no easier way? :-( As the third argument is a const reference to an object, how can I use arg2 to get what I wanted? Can I do tracemem ( copyin (arg2, 32), 32)? -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list [email protected]
