On Tue, May 13, 2008 at 10:43:36AM +0200, Mikael Ronstr?m wrote: > Hi, > I'm adding DTrace probes to MySQL and MySQL Cluster code and have some > strange issues when building the dtrace .o file using the dtrace -G - > s command. > A subset of the collections I use are the following: > > probe start_acckeyreq(int op_ptr); > probe end_acckeyreq(); > probe start_acckeyreq_lockwait(void*, int); > probe end_acckeyreq_lockwait(int op_ptr); > > The one that creates a problem is the start_acckeyreq_lockwait(void*, > int); > > In the code this looks like the following: > int int_val= operationRecPtr.i; > void *ptr_val= operationRecPtr.p; > jam(); > signal->theData[0] = RNIL; > NDB_BLOCKS_START_ACCKEYREQ_LOCKWAIT(ptr_val, int_val); > return; > > When executing dtrace -G -s ndb_blocks_dtrace.d DbaccMain.o > the output is (compilation of the cpp file goes fine: > > dtrace -G -s ndb_blocks_dtrace.d DbtupExecQuery.o DbtupCommit.o > DbaccMain.o DbdihMain.o DbtcMain.o DblqhMain.o > dtrace: failed to link script ndb_blocks_dtrace: an error was > encountered while processing DbaccMain.o > > I haven't figured out any way to get more information. By trial and > error I've discovered that it is this probe that is the > problem, but I don't see any issue with it. I've also had other > issues of similar kind with even simpler functions with only > an int parameter. I don't find any logic why the faulty ones are > faulty and the correct ones are correct, any ideas would be > helpful here. > > Rgrds Mikael Ronstrom
Add -xdebug to the command-line and you may get some additional error message ... otherwise we can mail another DTrace script to dtrace dtrace and see what is going on in there :) -Mike -- Mike Shapiro, Sun Microsystems Fishworks. blogs.sun.com/mws/ _______________________________________________ dtrace-discuss mailing list [email protected]
