Ozaki Kiichi wrote:
> Simply reproducable sample:
>
> test.vim
>
> ```
> try
> throw 'excp'
> catch
> "
> endtry
>
> fu! TimerFunc(...)
> echoerr 'oops'
> endfu
>
> call timer_start(1, 'TimerFunc')
> ```
>
> vim -Nu test.vim
>
> cause:
>
> At finishing above try-catch-endtry, "curren
Simply reproducable sample:
test.vim
```
try
throw 'excp'
catch
"
endtry
fu! TimerFunc(...)
echoerr 'oops'
endfu
call timer_start(1, 'TimerFunc')
```
vim -Nu test.vim
cause:
At finishing above try-catch-endtry, "current_exception" has directed a
dangling pointer (already freed).
Theref
On So, 09 Jul 2017, Aron Griffis wrote:
>
>
> On Sun, Jul 9, 2017 at 3:24 PM, Dominique Pellé
> wrote:
>
> Can you reproduce the crash with valgrind? It may give
> useful information. Just run vim as:
>
> $ valgrind --num-callers=50 --track-origins=yes ./vim 2> vg.log
>
> an
On Sun, Jul 9, 2017 at 3:24 PM, Dominique Pellé
wrote:
>
> Can you reproduce the crash with valgrind? It may give
> useful information. Just run vim as:
>
> $ valgrind --num-callers=50 --track-origins=yes ./vim 2> vg.log
>
> and vg.log will contain useful info if you manage to reproduce the bug.
>
Aron Griffis wrote:
> On Sun, Jul 9, 2017 at 3:06 PM, Aron Griffis wrote:
>>
>>
>>
>> On Sun, Jul 9, 2017 at 1:19 PM, Bram Moolenaar wrote:
>>>
>>>
>>> Aron Griffis wrote:
>>>
>>> > On Saturday, July 8, 2017 at 4:3
On Sun, Jul 9, 2017 at 3:17 PM, Aron Griffis wrote:
> In fact, I just rebuilt from pristine 702 source to make sure:
>
> $ CFLAGS=-ggdb ./configure --enable-gui=no --without-x
> $ make
> $ cd src
> $ gdb ./vim
> (gdb) run
>
> (change the content of .vim/background and .vim/scheme, cause segfault)
On Sun, Jul 9, 2017 at 3:06 PM, Aron Griffis wrote:
>
>
> On Sun, Jul 9, 2017 at 1:19 PM, Bram Moolenaar wrote:
>
>>
>> Aron Griffis wrote:
>>
>> > On Saturday, July 8, 2017 at 4:38:36 PM UTC-4, Bram Moolenaar wrote:
>> > > Patch 8.0.0702
On Sun, Jul 9, 2017 at 1:19 PM, Bram Moolenaar wrote:
>
> Aron Griffis wrote:
>
> > On Saturday, July 8, 2017 at 4:38:36 PM UTC-4, Bram Moolenaar wrote:
> > > Patch 8.0.0702
> > > Problem:An error in a timer can make Vim unusable.
> > > Solution:
On So, 09 Jul 2017, Dominique Pellé wrote:
> Bram Moolenaar wrote:
>
> > Aron Griffis wrote:
> >
> >> On Saturday, July 8, 2017 at 4:38:36 PM UTC-4, Bram Moolenaar wrote:
> >> > Patch 8.0.0702
> >> > Problem:An error in a timer can make V
Bram Moolenaar wrote:
> Aron Griffis wrote:
>
>> On Saturday, July 8, 2017 at 4:38:36 PM UTC-4, Bram Moolenaar wrote:
>> > Patch 8.0.0702
>> > Problem:An error in a timer can make Vim unusable.
>> > Solution: Don't set the error flag or
Aron Griffis wrote:
> On Saturday, July 8, 2017 at 4:38:36 PM UTC-4, Bram Moolenaar wrote:
> > Patch 8.0.0702
> > Problem:An error in a timer can make Vim unusable.
> > Solution: Don't set the error flag or exception from a timer. Stop a
> > timer
> &g
On Saturday, July 8, 2017 at 4:38:36 PM UTC-4, Bram Moolenaar wrote:
> Patch 8.0.0702
> Problem:An error in a timer can make Vim unusable.
> Solution: Don't set the error flag or exception from a timer. Stop a timer
> if it causes an error 3 out of 3 times. Dis
Patch 8.0.0702
Problem:An error in a timer can make Vim unusable.
Solution: Don't set the error flag or exception from a timer. Stop a timer
if it causes an error 3 out of 3 times. Discard an exception
caused inside a timer.
Files: src/ex_cmds2.c
13 matches
Mail list logo