Displaying 3 results from an estimated 3 matches for "rm_free".
Did you mean:
vm_free
2007 May 23
2
Possible ld.exe problem when building
...onsole.o:console.c:(.text+0xcff): more undefined references to `mbrtowc' follow
extra.o:extra.c:(.text+0x2240): undefined reference to `mallinfo'
extra.o:extra.c:(.text+0x226f): undefined reference to `mallinfo'
../main/libmain.a(memory.o):memory.c:(.text+0x260): undefined reference to `Rm_free'
../main/libmain.a(memory.o):memory.c:(.text+0xa80): undefined reference to `Rm_malloc'
../main/libmain.a(memory.o):memory.c:(.text+0xbde): undefined reference to `Rm_malloc'
../main/libmain.a(memory.o):memory.c:(.text+0xc3d): undefined reference to `Rm_malloc'
../main/libmain.a(mem...
2020 Jun 07
4
[External] Re: use of the tcltk package crashes R 4.0.1 for Windows
I've committed the change to use Free instead of free in tcltk.c and
sys-std.c (r78652 for R-devel, r78653 for R-patched).
We might consider either moving Calloc/Free out of the Windows
remapping or moving the remapping into header files so everything
seeing our header files uses our calloc/free. Either would be less
brittle that the current status.
Best,
luke
On Sun, 7 Jun 2020, peter
2020 Jun 07
0
[External] use of the tcltk package crashes R 4.0.1 for Windows
Ah, I see it now:
The remapping of free() to Rm_free() and calloc() to Rm_calloc() happens in memory.c, but not in tcltk.c; the macro Calloc in R_ext/RS.h maps to a call to R_chk_alloc which is defined in memory.h; RS.h is included in tcltk.c, so tcltk.c winds up calling Rm_calloc() via Calloc(), but then the NON-remapped free(), and the walls come t...