We're going to need some more information to diagnose your problem. For example, can you send the mem.d script? It's actually important to use pldd rather than ldd since pldd will actually show the libraries being used at runtime. Is this problem always reproducible? Are you able to just enable that probe individually?
Adam On Feb 26, 2008, at 8:09 PM, LiJIan wrote: > I used "ldd" to see the libraray linked, result shows libmtmalloc.so. > 1 is linked correctly. > > Strange thing is if I start dtrace script at the same time runing > the programme i.e. using "dtrace -qs ./mem.d -c ./test", > libmtmalloc.so.1:malloc:entry can be found. I don't know the > difference between the two ways. > > Although "target" way (run script at the same run programme) works, > but because when program starts up there are many memory allocation > which will not be released until the termination, I don't want this > way. > > JianLi > > > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > [email protected] -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
