Re: SEGV was occurred in libedit

2018-10-10 Thread Todd C. Miller
On Wed, 10 Oct 2018 13:46:10 +0900, YASUOKA Masahiko wrote: > See #1086, "lastline" is set to previous lastline. Then new line is not init > ialized. > > I think the following diff is better since it initializes the line in > the same way for first line. This bug was introduced in rev 1.21. I a

Re: SEGV was occurred in libedit

2018-10-09 Thread Masato Asou
Hi, From: YASUOKA Masahiko Date: Wed, 10 Oct 2018 13:46:10 +0900 (JST) > initialize new line. > > See #1086, "lastline" is set to previous lastline. Then new line is not > initialized. > > I think the following diff is better since it initializes the line in > the same way for first line. >

Re: SEGV was occurred in libedit

2018-10-09 Thread YASUOKA Masahiko
Hi, On Wed, 10 Oct 2018 08:00:14 +0900 (JST) Masato Asou wrote: > When I use /usr/bin/bc command with MALLOC_OPTIONS=UJ, SEGV was > occurred in libedit. > > $ MALLOC_OPTIONS=UJ /usr/bin/bc > 10 + 20 + 30 + 40 + 50 + 60 + 70 + 80 + > 90 +

Re: SEGV was occurred in libedit

2018-10-09 Thread Todd C. Miller
On Wed, 10 Oct 2018 08:00:14 +0900, Masato Asou wrote: > diff --git a/lib/libedit/refresh.c b/lib/libedit/refresh.c > index f2d001d67cb..5f2d607d356 100644 > --- a/lib/libedit/refresh.c > +++ b/lib/libedit/refresh.c > @@ -1061,6 +1061,7 @@ re_fastputc(EditLine *el, wint_t c) > > terminal__

SEGV was occurred in libedit

2018-10-09 Thread Masato Asou
Hi, When I use /usr/bin/bc command with MALLOC_OPTIONS=UJ, SEGV was occurred in libedit. $ MALLOC_OPTIONS=UJ /usr/bin/bc 10 + 20 + 30 + 40 + 50 + 60 + 70 + 80 + 90 + Segmentation fault (core dumped) $ /usr/bin/gdb /usr/bin/bc bc.core GNU gdb 6.3 ... snip