Various blocks of memory are not freed until the program is shut down, but
are in use up to that point so it is not a 'leak'. Most of the warnings
are not from R itself but from e.g. readline or X11, and all are tiny.
That makes sense, thank you for clarifying.
best regards,
daniel
If run valgrind R then I get all sorts of warnings. I was wondering
whether I should worry about them or not.
Don't worry about them. Those are benign issues with the system
libraries.. insofar as you trust those libraries, which you should... in
general.
Jeff
Jeff,
Thanks for your
Sorry I forgot to mention this happens just starting and then stopping
R. I am not running any other commands or loading any packages.
I was trying to check my own C program (as a standalone program it
does not produce any valgrind warnings), but now I am not sure what is
going on when using
Dear R developers
I am running an instrumented build of R 2.6.1 on ubuntu, compiled with
option configure --with-valgrind-instrumentation=3.
If run valgrind R then I get all sorts of warnings. I was wondering
whether I should worry about them or not.
First, when I open R as follows:
$R -d
, my question is: what is the proper or preferred method of
solving this problem, and how do I find out how to apply it?
Thank you very much for your attention.
Best regards,
Daniel Oberski
University of Tilburg / European Social Survey
[EMAIL PROTECTED
