search for: pushreadlin

Full_Name: Kai Mäkisara Version: 1.6.0 OS: Tru64 Submission from: (NULL) (128.214.53.92) Any command given in terminal window dumps core if readline is compiled in. The reason is a bug in pushReadline: the first call pushes the function below the stack. The following patch solves the problem: --- R-1.6.0/src/unix/sys-std.c~ Sun Aug 25 12:51:20 2002 +++ R-1.6.0/src/unix/sys-std.c Tue Oct 15 14:43:00 2002 @@ -389,10 +389,10 @@ void pushReadline(char *prompt, rl_vcpfunc_t f) { - if(Readline...

...umstance has arisen in the nesting of readline input. Please report using bug.report() > The warning is difficult to reproduce because it seems to appear at random times, usually after I enter about 100 or so commands into the console. I noticed that the function which produces this warning, `pushReadline' in src/unix/sys-std.c, was modified on October 16, 2002 in regards to bug report PR#2165. I can't tell if this change is the source of the warning bit I don't ever recall seeing this warning on earlier versions. I build R from source using the readline-devel-4.1-9 package which came...

...extremely long to return: # R --vanilla big <- paste(sample(LETTERS, size = 1e7, replace = TRUE), collapse = "") options(prompt = big) Running R with gdb and interrupting to get backtraces shows that 'pushReadLine' in 'unix/sys-std.c' results in a chain of libreadline calls, including, in my case at least, UTF-8 and a lot of __strlen_avx2 activity. 'R_PromptString' in 'main.c' should check prompt is a reasonable length, as well as a check when setting the prompt in 'options.c...