search for: do_readchar

Full_Name: Hugh C. Pumphrey Version: 1.4.1 OS: Linux (Debian Woody) Submission from: (NULL) (129.215.133.170) The function readChar() appears to have some type of problem with memory allocation. I don't know if "memory leak" is the correct term but if one uses readChar() many times, the R binary grows in size until it eats all your memory and swap space. The code enclosed below

...ons.c:2556: structure has no member named `open64' connections.c: In function `do_readbin': connections.c:2692: structure has no member named `open64' connections.c: In function `do_writebin': connections.c:2895: structure has no member named `open64' connections.c: In function `do_readchar': connections.c:3140: structure has no member named `open64' connections.c: In function `do_writechar': connections.c:3212: structure has no member named `open64' connections.c: In function `switch_or_tee_stdout': connections.c:3390: structure has no member named `open64' co...

...o I think the strncpy() call will read too far. [This happened because I didn't remember that R lets null terminate strings; so I did a readChar(infh, nchars=6144) through some nulls at the start of the header, and ended up with a much shorter string than I was expecting. As far as I can tell do_readchar still behaves in these circumstances, and in any case I can produce the fault without it.] Using readBin and writeBin with integer() and size=1 seems to be the solution for header copying, but the faults still seemed worth reporting. I'm currently using R 1.8.0 on NetBSD/i386 1.6.1. Mark &lt...