Debugging (Line by Line) of Rcpp-Generated Dll Under Windows

Debugging windows mobile DLLs attached to binaries stored in device ROM

Have a look in this forum thread, someone suggests a workaround that might work for you.

RCPP generated DLL files triggering Bit9 errors

I'm an Bit9 employee so what I tell you is the truth.

The Bit9 admin, using the event stream in the Bit9 console, can see what process is writing those DLLs to disk and mark that process as an installer. What that means is that process is promoted such that any "interesting" files (exe, dll, driver file, system file, script) it writes to disk will be approved. They can be specific enough that it is limited to a particular directory and it's subdirectories.

If your Bit9 administrator doesn't know how to write such a rule, or is concerned about the security implications of such a rule have them go to the Bit9 ( we've changed our name to Carbon Black) User Exchange and they can get additional feedback.

RCpp Temporary Build Location

Try setting TMPDIR which R respects. This is indeed not an Rcpp issue but a generic R CMD build / R CMD INSTALL issue.

From help(tempfile):

The environment variables TMPDIR, TMP and TEMP are checked in
turn and the first found which points to a writable directory is
used: if none succeeds /tmp is used.

PS Rcpp with lower-case C.

---

Related Topics