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 + Segmentation fault (c

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__

Re: user land system spinning time

2018-10-09 Thread Scott Cheloha
On Mon, Oct 08, 2018 at 09:44:35PM +0200, Alexander Bluhm wrote: > Hi, > > On May 14 we did split kernel spinning time from system time. Goal > was to see what the kernel is doing. > > I just realized that user land time accounting has also changed. > The commit changed system time of a process

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 ...

Re: [vi] moving by sentences is inconsistent

2018-10-09 Thread Jeremy C. Reed
On Mon, 8 Oct 2018, Jonathan Thornburg wrote: > An excellent (although secondary) source from the precambrian era, >Morris I Bolsky >"The /vi/ User's Hanbdbook" >(c) 1984 by Bell Telephone Laboratories, Incorporated >(c) 1985 by AT&T Technologies, Inc >published by Prentice-Hal

Re: copy and paste error in rb tree code

2018-10-09 Thread Theo Buehler
On Tue, Oct 09, 2018 at 01:02:11PM +1000, David Gwynne wrote: > According to https://github.com/FRRouting/frr/pull/3106, Coverity thinks > I made a copy and paste error regarding one of the augment calls in > RBT_REMOVE. I'm inclined to agree. > > The augment code is only used by uvm_map.c, and it