Hello,
My R code calles a C/Fortran dll and I want to debug C code using Visual
Studio and Intel compilers /debugger
Debugging with Rcpp and RInsight does not work correctly on Windows.
Is there some other way to set breakpoints in C code and access to
variables ?
Thank you !
Kind regards,
On 13-01-18 6:24 AM, Vitaliy FEOKTISTOV wrote:
Hello,
My R code calles a C/Fortran dll and I want to debug C code using Visual
Studio and Intel compilers /debugger
Debugging with Rcpp and RInsight does not work correctly on Windows.
Is there some other way to set breakpoints in C code and
To what end is the --vanilla here? Writing R Extensions says that R CMD
check (and R CMD build) are invoked via R --vanilla so that would seem
redundant, although my experience from several hours working this
through today suggests there is a difference between R --vanilla CMD
check and R CMD
(somewhat related to thread [Rd] R CMD check not reading R_LIBS )
For many years I have maintained R versions by building R (./configure ;
make) in a directory indicating the version number, putting the
directory/bin on my path, and setting R_LIBS_SITE.
It seems only one version can easily
Have you looked at Environment Modules (http://modules.sourceforge.net/)? I
use it to maintain multiple versions of R. Users can choose their default and
switch among them at the command line.
Aaron
On Fri, Jan 18, 2013 at 02:04:13PM -0500, Paul Gilbert wrote:
(somewhat related to thread
Hi,
The current implementation for utils::tar() seems to generate broken
tarballs when some of the files to include in the tarball are = 2GB.
For example, when running 'R CMD build' on a big Bioconductor data
package, we see this warning:
* checking for file ‘ChIPXpressData/DESCRIPTION’ ...
