search for: rstd_cleanup

Dear R Core, GCC 15 is already in Fedora rawhide, because it will be part of the next release, Fedora 42. R 4.4.2 fails to build with the following error [1]: > sys-std.c:1189:1: warning: ?noreturn? attribute ignored [-Wattributes] > 1189 | void Rstd_CleanUp(SA_TYPE saveact, int status, int runLast) > | ^~~~ > sys-std.c:1189:1: error: expected identifier or ?(? before ?void? I've seen some references to this in the source code, so this may be fixed in R devel. If this is the case, it would be great if you could provide a patch that I c...

...car wrote: > Dear R Core, > > GCC 15 is already in Fedora rawhide, because it will be part of the next > release, Fedora 42. R 4.4.2 fails to build with the following error [1]: > >> sys-std.c:1189:1: warning: ?noreturn? attribute ignored [-Wattributes] >> 1189 | void Rstd_CleanUp(SA_TYPE saveact, int status, int runLast) >> | ^~~~ >> sys-std.c:1189:1: error: expected identifier or ?(? before ?void? You failed to say that GCC 15 defaults to C23 (and they have not yet documented that). > > I've seen some references to this in the source code, s...

...DEFAULT,/* was === SA_RESTORE */ SA_NOSAVE, SA_SAVE, SA_SAVEASK, SA_SUICIDE } SA_TYPE; ------------------------------------------------------------- from non-exported header file ${R_HOME}/src/unix/Runix.h ------------------------------------------------------------- extern void Rstd_CleanUp(SA_TYPE saveact, int status, int runLast); Use: ------------- When the PostgreSQL backend process exits, Rstd_CleanUp() is called via registered onexit callback so that the embedded R interpreter can clean up (e.g. to remove the created Rtmp[pid] directory). Note: ------------- Similar use foun...

...and at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311 311 { (gdb) where #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311 #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178 #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243 #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87 #4 0x00005555556cc85e in do_quit (call=<optimized out>,...

.../RtmppoKPXb") at sysutils.c:311 >> 311 { >> (gdb) where >> #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311 >> #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178 >> #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243 >> #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87 >> #4 0x00005555556cc85e in do_quit (call=<o...

Hello. I am not sure if this is a bug. I loaded into R a very large matrix, around 600,000 X 30 integers. My machine has 2G ram. After trying to write.table a modification of this matrix, R generated some sort of malloc error. Then, Error: vector memory exhausted (limit reached?) > q() Save workspace image? [y/n/c]: n *** malloc: vm_allocate(size=8421376) failed (error code=3) ***

...e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311 > 311 { > (gdb) where > #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311 > #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178 > #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243 > #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87 > #4 0x00005555556cc85e in do_quit (call=<optimized...

...;>>> 311 { >>>> (gdb) where >>>> #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311 >>>> #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178 >>>> #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243 >>>> #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87 >>>> #4 0x00005555556cc85e in do_...

...utils.c:311 > >> 311 { > >> (gdb) where > >> #0 R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb") at sysutils.c:311 > >> #1 0x00005555557c30ec in R_CleanTempDir () at sys-std.c:1178 > >> #2 0x00005555557c31d7 in Rstd_CleanUp (saveact=<optimized out>, status=0, runLast=<optimized out>) at sys-std.c:1243 > >> #3 0x00005555557c593d in R_CleanUp (saveact=saveact at entry=SA_NOSAVE, status=status at entry=0, runLast=<optimized out>) at system.c:87 > >> #4 0x00005555556cc85e in do_quit (...

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

...plIteration(...): ------------------------------------------------------------------ value = eval(R_CurrentExpr, rho); +if(value == NULL) +return(-1); src/main/main.c : do_quit(): ------------------------------------- //exit(0); +return(NULL) I also removed the call to exit in src/linux/sys-std.c:Rstd_CleanUp and src/gnuwin32/system.c:R_CleanUp for linux and windows respectively. This is obviously a quick hack to make it work (but it works fine, also the standalone R exits ok this way), but I can imagine more people want to use the mainloop with the possibility to return from it without making their ap...

Hi all, a user contacted me about a segfault when installing WGCNA package dowloaded from CRAN. I also see a segfault like that on certain installs of R. The package passes all CRAN checks, so presumably this has something to do with the R installation or environment. The R versions here are not the newest but I would guess that this is not an R version issue. I'm attaching two