search for: readline_handl

...0; (gdb) bt #0 0x400da7bc in _IO_fflush (fp=0x819ecd8) at iofflush.c:41 #1 0x8122165 in rl_prep_terminal (meta_flag=0) at rltty.c:555 #2 0x811cb08 in _rl_callback_newline () at callback.c:76 #3 0x811cb4a in rl_callback_handler_install (prompt=0x4093c210 "> ", linefunc=0x80e8798 <readline_handler>) at callback.c:95 #4 0x80e89b5 in Rstd_ReadConsole (prompt=0x4093c210 "> ", buf=0xbfffeedc "", len=1024, addtohistory=1) at ../../../R-1.1.0/src/unix/sys-std.c:357 #5 0x80e6b2e in R_ReadConsole (prompt=0x4093c210 "> ", buf=0xbfffeedc "", len=102...

...for 4.2, and so compilation fails (under gcc 2.95.3 at least). The quick fix is (ca line 88) char *tilde_expand(const char*); ^^^^^ but we should really check the readline version number and only define this in earlier versions. There is also a conflict in src/unix/sys-std.c: readline_handler is defined with unsigned char * but it should be char * according to the readline 4.2 prototype. -- Brian D. Ripley, ripley@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 Sout...

...ntioned when using the readline() call: http://www.delorie.com/gnu/docs/readline/rlman_24.html#IDX174 No further mention at the reference for the alternative interface: http://www.delorie.com/gnu/docs/readline/rlman_41.html#IDX288 When I added 'free(line)' to src/unix/sys-std.c:readline_handler() valgrind stopped complaining about the leaks and did not complain about using freed memory. It does start complaining a new leak in the readline code, but it looks like that may be a constant 2 block, 40 byte leak, not something that grows as the session goes on: ==11246== ERROR SUMMARY: 0 er...