Re: Bash bind bug: infinite loop with memory leak in Readline

On 9/22/16 11:23 AM, Christian Klomp wrote: > Limiting the nesting level sounds like a straightforward solution. > Although I'm not sure whether exposing a configurable level is > necessary. Do people actually nest their macros that deep that no > reasonably safe upper bound can be set? There's

Re: Bash bind bug: infinite loop with memory leak in Readline

2016-09-19 3:41 GMT+02:00 Chet Ramey : > Yes, you've triggered an infinite loop with the key binding. One of the > strengths of macros is that the expansion is not simply a string -- it can > be used as shorthand for a complex key sequence, so simply disallowing > the general

Re: Bash bind bug: infinite loop with memory leak in Readline

On 8/10/16 11:42 AM, Christian Klomp wrote: > Hi, > > I found a problem with the binding of key sequences to macros that > results in bash allocating all the memory until the process is killed. > It happens when a key is mapped to itself, e.g., `bind '"3":"3"'`. Now > when '3' is typed the while

Bash bind bug: infinite loop with memory leak in Readline

Hi, I found a problem with the binding of key sequences to macros that results in bash allocating all the memory until the process is killed. It happens when a key is mapped to itself, e.g., `bind '"3":"3"'`. Now when '3' is typed the while loop inside the readline_internal_charloop function will