On 5/11/17 10:42 AM, Eduardo Bustamante wrote:
> On Thu, May 11, 2017 at 9:31 AM, Chet Ramey wrote:
> [...]
>> Yes, this is it. I fixed it yesterday.
>
> Thanks. From the crashing inputs that I reported, is there any that is
> still unfixed that I can help with? When are you going to upload the
>
On Thu, May 11, 2017 at 9:31 AM, Chet Ramey wrote:
[...]
> Yes, this is it. I fixed it yesterday.
Thanks. From the crashing inputs that I reported, is there any that is
still unfixed that I can help with? When are you going to upload the
next snapshot? (To see if I can resume fuzzing next weekend
On 5/11/17 8:03 AM, Eduardo Bustamante wrote:
> On Tue, May 9, 2017 at 9:28 AM, Eduardo Bustamante wrote:
> [...]
>
> From what I can tell, it seems like the problem is that `set-mark'
> allows you to set a negative rl_mark, and then you can use
> `exchange-point-and-mark' to place that negative
On Tue, May 9, 2017 at 9:28 AM, Eduardo Bustamante wrote:
[...]
>From what I can tell, it seems like the problem is that `set-mark'
allows you to set a negative rl_mark, and then you can use
`exchange-point-and-mark' to place that negative rl_mark into
rl_point.
A simple way of breaking this is
dualbus@debian:~/bash-fuzzing/read-readline$ base64 loop
AAAbLbUA9loQGDIYLhwYGBkYGJgYGBj4FwAYYBlEAERLG0YK
dualbus@debian:~/bash-fuzzing/read-readline$ od -c loop
000 \0 \0 033 - 265 \0 366 Z 020 030 2 030 . 034 030 030
020 031 030 030 230 030 030 030 370 027 \0 030 ` 031 D
