Did you build R with profiling (not R profiling, which must be disabled)
compiler/linker options, as mentioned in the R-admin manual?
I've certainly profiled dyn.load-ed code on Solaris in R, but not
recently.
On Fri, 28 Feb 2003 rex.dwyer at syngenta.com wrote:
> I have inherited a legacy S-plus system with about 10,000 lines of S and
> 10,000 lines of
> Fortran. It's now running under R. However, I would like to profile
the
> fortran code with gprof or prof for performance tuning. I've
successfully
> linked the .so file into a simple C driver program and profiled, but I
can't
> seem to get profiling to work when using dyn.load() to use it from R. Do I
> have to use .C() to call some monitor initialization procedure explicitly?
> The /var/tmp/foo.so.profile file is never created.
>
> I'm using R 1.6.2 and I have the same problem under both SunOS 5.8 and
under
> Red Hat Linux 7.3 with 2.4.18-openmosix4smp kernel.
>
> Has anyone had any success with this sort of profiling?
--
Brian D. Ripley, ripley at stats.ox.ac.uk
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UK Fax: +44 1865 272595