I have inserted some probes in my application, and it works great in the "debug build" I have been using. So I wanted to look at the "overhead" introduced by inactive dtrace probes in my application. I am using the Sun Studio 11 compiler, so I added the following options: -xO5 -g0 -xbuiltin But this breaks the linking of my application. Undefined first referenced symbol in file __SLIP.DELETER__B dtrace.o __SLIP.DELETER__D dtrace.o __SLIP.DELETER__E dtrace.o (the dtrace.o is the object file created by: dtrace -G -32 -o dtrace.o -s dtrace.s <objs>) so.. what do I do? Trond This message posted from opensolaris.org
Adam Leventhal
2006-Aug-31 16:44 UTC
[dtrace-discuss] Problem linking USDT C++ application
After some back and forth with Trond, we discovered that the problem is that the C++ compiler makes virtual destructors have file local scope. Accordingly he was hitting this bug: 6370454 dtrace should support USDT probes in static functions This was fixed in build 32. Adam On Mon, Aug 28, 2006 at 09:19:10AM -0700, Trond Norbye wrote:> I have inserted some probes in my application, and it works great in the "debug build" I have been using. So I wanted to look at the "overhead" introduced by inactive dtrace probes in my application. I am using the Sun Studio 11 compiler, so I added the following options: > -xO5 -g0 -xbuiltin > > But this breaks the linking of my application. > Undefined first referenced > symbol in file > __SLIP.DELETER__B dtrace.o > __SLIP.DELETER__D dtrace.o > __SLIP.DELETER__E dtrace.o > > (the dtrace.o is the object file created by: dtrace -G -32 -o dtrace.o -s dtrace.s <objs>) > > so.. what do I do? > > Trond > > > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org-- Adam Leventhal, Solaris Kernel Development http://blogs.sun.com/ahl