Dave Jarvis <dave@joot.com> writes:
> It looks to be a recursive bug in libreadline, as called by the
> _rl_dispatch_subseq () function. With debug compiled in, here is a bit
> of the stack trace:
> #0 0x4005275c in _rl_dispatch () from /usr/lib/libreadline.so.4
> #1 0x40052803 in _rl_dispatch_subseq () from /usr/lib/libreadline.so.4
> #2 0x4005277e in _rl_dispatch () from /usr/lib/libreadline.so.4
> #3 0x40052803 in _rl_dispatch_subseq () from /usr/lib/libreadline.so.4
> #4 0x4005277e in _rl_dispatch () from /usr/lib/libreadline.so.4
> #5 0x40052803 in _rl_dispatch_subseq () from /usr/lib/libreadline.so.4
> #6 0x4005277e in _rl_dispatch () from /usr/lib/libreadline.so.4
Hmm. A quick google search finds a suspiciously similar complaint at
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=200208021107.g72B723d021352%40darkstar.example.net&rnum=2&prev=/groups%3Fq%3D_rl_dispatch_subseq%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3D200208021107.g72B723d021352%2540darkstar.example.net%26rnum%3D2
Dunno if you can try the readline patch suggested there ...
regards, tom lane
