Christian Lippka
2005-Sep-07 14:34 UTC
[dtrace-discuss] Problems with pid provider and long mangled probe names
Hi, I''m currently evaluating to use DTrace to find some performance bottlenecks in StarOffice/OpenOffice on Solaris. I currently use the pid provider but I found the following problem: dtrace: failed to compile script slidesorter.d: line 55: invalid probe description > "pid$1::__1cCsdLslidesorterFcacheOQdDueueProcessor4n0CTGenericRequestQdDueue4n0BEviewbBPageObjectViewObjectContact___n0E_n0CLBitmapCache_n0CVPreviewBitmapFactory2__OProcessRequest6M_v_:entry": File name too long Obviously the mangled name __1cCsdLslidesorterFcacheOQdDueueProcessor4n0CTGenericRequestQdDueue4n0BEviewbBPageObjectViewObjectContact___n0E_n0CLBitmapCache_n0CVPreviewBitmapFactory2__OProcessRequest6M_v_ can not be processed as a probe by DTrace. Is there a way to work around this limit? Is it possible to change this limit? Regards, Christian
Adam Leventhal
2005-Sep-07 14:43 UTC
[dtrace-discuss] Problems with pid provider and long mangled probe names
Hi Christian, One way to work around it might be to use a wild-card character, but since I suspect you''re bumping into a limitation of DTrace rather than the pid privder I doubt that will help. This isn''t going to be pretty, but it''s possible to use the pid provider to trace an explicit address; I suggest you use mdb(1) (or whatever) to find the address of that function and then use the pid provider on that address: # mdb -p 1359 Loading modules: [ ld.so.1 libc.so.1 ]> execute=K8072ad4># dtrace -n pid1359::-:8072ad4 dtrace: description ''pid1368::-:8072ad4'' matched 1 probe Obviously this isn''t ideal, but it is a work around that will address your problem. Tracing addresses can also be used when dealing with stripped binaries. I hope that helps. Sorry about the problem. We''ve been discussing on and off how to address the issue of very very long symbol names -- it looks like we need to actually conclude that discussion. Adam On Wed, Sep 07, 2005 at 04:34:14PM +0200, Christian Lippka wrote:> Hi, > > I''m currently evaluating to use DTrace to find some performance > bottlenecks in StarOffice/OpenOffice on Solaris. > I currently use the pid provider but I found the following problem: > > dtrace: failed to compile script slidesorter.d: line 55: invalid probe > description > > "pid$1::__1cCsdLslidesorterFcacheOQdDueueProcessor4n0CTGenericRequestQdDueue4n0BEviewbBPageObjectViewObjectContact___n0E_n0CLBitmapCache_n0CVPreviewBitmapFactory2__OProcessRequest6M_v_:entry": > File name too long > > Obviously the mangled name > > __1cCsdLslidesorterFcacheOQdDueueProcessor4n0CTGenericRequestQdDueue4n0BEviewbBPageObjectViewObjectContact___n0E_n0CLBitmapCache_n0CVPreviewBitmapFactory2__OProcessRequest6M_v_ > > can not be processed as a probe by DTrace. Is there a way to work around > this limit? Is it possible to change this limit? > > Regards, > Christian > > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org-- Adam Leventhal, Solaris Kernel Development http://blogs.sun.com/ahl