Skip to content
Prev 14298 / 15075 Next
Original Raw

problem with Rprof

Simon Urbanek 
Carl,

first, setting such low interval won't work anyway - the overhead is bigger than the sampled time, so we should really not allow it to begin with (on my machine the timer signals arrive before anything can be done so you have to kill R and you get no output).

That said, it crashes in doprof() which is called on all threads - the main R one is ok, but one of the other threads crashes in pthread_self(). At that time R is trying to propagate the signal from all threads to the main thread which seems odd to me (since the main thread already got the signal), I'm CCing Luke in the hope that he has any ideas. This may fall in the category of "don't do this" and the fix may be to set a lower bound on the interval.

Cheers,
Simon

Thread (10 messages)

Carl Witthoft problem with Rprof Nov 5 Simon Urbanek problem with Rprof Nov 6 iuke-tier@ey m@iii@g oii uiow@@edu problem with Rprof Nov 6 Tomas Kalibera problem with Rprof Nov 8 Simon Urbanek problem with Rprof Nov 8 iuke-tier@ey m@iii@g oii uiow@@edu problem with Rprof Nov 9 Tomas Kalibera problem with Rprof Nov 10 Carl Witthoft problem with Rprof Nov 10 Tomas Kalibera problem with Rprof Nov 10 iuke-tier@ey m@iii@g oii uiow@@edu problem with Rprof Nov 10