yes, this was attempted. The program ran for a short time ( 2 seconds ? ) and then just stopped - back to the prompt.
-----Original Message----- From: Yosef Lev (Sun Labs, Oracle) [mailto:yossi....@oracle.com] Sent: Tuesday, May 11, 2010 3:01 PM To: William Reich Cc: Trond Norbye; dtrace-discuss@opensolaris.org Subject: Re: [dtrace-discuss] dtrace / c++ / lots of threads I'm not sure what the problem might be (except for the process being traced by another program), but have you tried letting DTrace run the executable for you (with the "-c" switch)? To do that, you'll have to replace $1 with $target in your DTrace script, and then run it as follows: dtrace -s <script file> -c '<command to run your executable>' DTrace will create a process to run the command specified after the '-c' switch, assign the pid to $target and pass it to your script. Cheers, Yossi William Reich wrote: > as far as I know - no > > again, any other executable , say "hello world" , works with dtrace just > fine. > > Only this one particular executable is not working with dtrace. > > wr > > -----Original Message----- > From: Trond Norbye [mailto:trond.nor...@gmail.com] > Sent: Tuesday, May 11, 2010 1:32 PM > To: William Reich > Cc: dtrace-discuss@opensolaris.org > Subject: Re: [dtrace-discuss] dtrace / c++ / lots of threads > > > On 11. mai 2010, at 19.27, William Reich wrote: > > >> truss was not being used in this simple test. >> Neither was gdb. >> >> > > are you using watchmalloc or something else that utilize /proc ? > > Trond > > > >> wr >> >> >> >> -----Original Message----- >> >> Isn't this what happens if a process is already being traced (e.g., by >> truss)? >> >> Nico >> -- >> >> -----Original Message----- >> From: dtrace-discuss-boun...@opensolaris.org >> [mailto:dtrace-discuss-boun...@opensolaris.org] On Behalf Of William >> Reich >> Sent: Tuesday, May 11, 2010 9:58 AM >> To: Michael Schuster >> Cc: dtrace-discuss@opensolaris.org >> Subject: Re: [dtrace-discuss] dtrace / c++ / lots of threads >> >> we use the g++ compiler for this c++ executable >> >> g++ -v >> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs >> Configured with: >> > /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure > >> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as >> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ >> --enable-shared >> Thread model: posix >> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath) >> >> There are many files on a link line with some 3rd party libraries... >> >> g++ -m64 -fPIC /vob/adc/router/core/DiameterAdapter.o >> /vob/adc/router/core/DiameterAdapterThread.o \ >> /vob/adc/router/core/DiameterMessage.o >> /vob/adc/router/core/ServerGroup.o /vob/adc/router/core/RoundRobin.o \ >> /vob/adc/router/core/HashRouting.o >> /vob/adc/router/core/AlgorithmFactory.o >> /vob/adc/router/core/DiameterConfigException.o \ >> /vob/adc/router/core/DiameterException.o >> /vob/adc/router/core/DiameterMessageException.o >> /vob/adc/router/core/RoutingEngine.o \ >> . >> . >> . >> /vob/adc/router/framework/TraceLoggerThread.o \ >> -lsocket -lnsl -lpthread -L/vob/diameter/lib \ >> -L/vob/diameter/sctp/lib -L/vob/adc/router/thirdparty/boost/stage/lib >> > \ > >> -ldiameter -ldiamsctp -lboost_serialization -o ../bin/adc >> >> >> wr >> >> >> -----Original Message----- >> From: Michael Schuster [mailto:michael.schus...@oracle.com] >> Sent: Tuesday, May 11, 2010 9:36 AM >> To: William Reich >> Cc: dtrace-discuss@opensolaris.org >> Subject: Re: [dtrace-discuss] dtrace / c++ / lots of threads >> >> On 11.05.10 14:38, William Reich wrote: >> >>> as implied in the first email ( below ) , >>> the only thing that I see as different between this particular >>> > process > >>> and any other >>> is that >>> a) the executable is 8.5 megs as it sits on the disk >>> >> I don't think this should be an issue ... but can you give some detail >> on >> how this executable is built? >> >> >>> b) the executable has at least 10 threads in it. >>> >> the executable doesn't have threads ;-) they're a property of the >> running >> process, but I know what you mean: that shouldn't be a problem, I just >> > > >> tried tracing firefox, which has more, and had no issue. >> >> Michael >> -- >> michael.schus...@oracle.com http://blogs.sun.com/recursion >> Recursion, n.: see 'Recursion' >> _______________________________________________ >> dtrace-discuss mailing list >> dtrace-discuss@opensolaris.org >> _______________________________________________ >> dtrace-discuss mailing list >> dtrace-discuss@opensolaris.org >> > > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss@opensolaris.org > _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
