> If dtrace thinks something fishy is going on, it can refuse to instrument > the return sites. This is mainly due to issues with jump-tables. > If you set DTRACE_DEBUG= in your environment, is there anything of interest? > Look for "grabbed pid NNNN" as a starting place.
Thanks for the hint, I was not aware of DTRACE_DEBUG. I found the following, which confirms your assumption, that it might be an issue with jump-tables: libdtrace DEBUG: creating probe pid17864:myprog:dcntrl_:return libdtrace DEBUG: error at 0x851 (assuming jump table) I searched the forum but haven't found an explanation under what conditions dtrace assumes a jump-table. Are there any (Fortran) compiler settings which could help avoiding this issue? In what context should I read the given address 0x851? Neither the function dcntrl_ nor the calling function has an opcode starting at this address. Thanks, Manfred -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
