search for: r_cleantempdir

Hello, This is probably a very minor point, but R_CleanTempDir may still have a shell injection in it. I couldn't find a way to shoot the user in the foot in a significant way (by, say, accidentally removing ~), thanks to R disallowing spaces in the path, but if Sys_TempDir somehow acquires a value of "/tmp/';echo;'", R_CleanTempDir() wil...

On 2/16/23 15:09, Ivan Krylov wrote: > Hello, > > This is probably a very minor point, but R_CleanTempDir may still have > a shell injection in it. I couldn't find a way to shoot the user in the > foot in a significant way (by, say, accidentally removing ~), thanks to > R disallowing spaces in the path, but if Sys_TempDir somehow acquires a > value of "/tmp/';echo;'",...

The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) > q("no") Breakpoint 1, R_system (command=command at entry=0x7fffffffa1e0 "...

...23, 2020 at 7:10 PM Bill Dunlap <williamwdunlap at gmail.com> wrote: >> The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) >> >>> q("no") >> Breakpoint 1, R_system (command=command at en...

...3, 2020 at 7:10 PM Bill Dunlap <williamwdunlap at gmail.com> wrote: > > The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) > > > q("no") > Breakpoint 1, R_system (command=command at entry=0x7ffff...

...at 7:10 PM Bill Dunlap <williamwdunlap at gmail.com> wrote: >>>> The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) >>>> >>>>> q("no") >>>> Breakpoint 1, R_syste...

...020 at 7:10 PM Bill Dunlap <williamwdunlap at gmail.com> wrote: > >> The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) > >> > >>> q("no") > >> Breakpoint 1, R_system (comman...

Dear R-developers, Some of the more fat scripts (50+ GB mem used by R) that I am running, when they finish they do quit with q("no", status=0) Quite often it happens that there is an extra stderr output produced at the very end which looks like this: Warning message: In .Internal(quit(save, status, runLast)) : system call failed: Cannot allocate memory Is there any way to avoid this

Dear R devel, I have a C++ app that calls into embedded R to perform some analytic calculations. When my app encounters a segmentation fault, R always prints the following crash prompt and asks me to enter an action: *** caught segfault *** address 0x8, cause 'memory not mapped' Possible actions: 1: abort (with core dump, if enabled) 2: normal R exit 3: exit R without saving workspace

...) libintl_nl_current_default_domain ../extra/intl/libintl.a(textdomain.o) Rf_qwilcox arithmetic.o libintl_nl_default_default_domain ../extra/intl/libintl.a(textdomain.o) BZ2_bzWriteOpen connections.o bincode registration.o R_CleanTempDir main.o do_proctime names.o norm_rand optim.o Rf_rnchisq random.o Rf_rnbinom random.o R_running_as_main_program Rmain.o Rf_psigamma arithmetic.o...

...) libintl_nl_current_default_domain ../extra/intl/libintl.a(textdomain.o) Rf_qwilcox arithmetic.o libintl_nl_default_default_domain ../extra/intl/libintl.a(textdomain.o) BZ2_bzWriteOpen connections.o bincode registration.o R_CleanTempDir main.o do_proctime names.o norm_rand optim.o Rf_rnchisq random.o Rf_rnbinom random.o R_running_as_main_program Rmain.o Rf_psigamma arithmetic.o...

...tic.o libintl_nl_domain_bindings ../extra/intl/libintl.a(bindtextdom.o) libintl_nl_current_default_domain ../extra/intl/libintl.a(textdomain.o) Rf_qwilcox arithmetic.o libintl_nl_default_default_domain ../extra/intl/libintl.a(textdomain.o) BZ2_bzWriteOpen connections.o bincode registration.o R_CleanTempDir main.o do_proctime names.o norm_rand optim.o Rf_rnchisq random.o Rf_rnbinom random.o R_running_as_main_program Rmain.o Rf_psigamma arithmetic.o ch2inv_ registration.o BZ2_bzWrite connections.o inflateInit2_ connections.o Rf_rwilcox random.o R_CleanUp errors.o _nl_find_msg ../extra/intl/...

...) libintl_nl_current_default_domain ../extra/intl/libintl.a(textdomain.o) Rf_qwilcox arithmetic.o libintl_nl_default_default_domain ../extra/intl/libintl.a(textdomain.o) BZ2_bzWriteOpen connections.o bincode registration.o R_CleanTempDir main.o do_proctime names.o norm_rand optim.o Rf_rnchisq random.o Rf_rnbinom random.o R_running_as_main_program Rmain.o Rf_psigamma arithmetic.o...