On Tuesday, August 9, 2016 at 8:16:28 AM UTC+12, gschintgen wrote:
> Hi, I think my current Ubuntu installation is suffering from the same bug.
> I'm on 16.04 (clean install) using the distribution-provided package: version
> 7.4.1689-3ubuntu1.1.
> Fairly often (but not always) gvim crashes as
On Wednesday, June 8, 2016 at 6:41:47 PM UTC+12, tracyone wrote:
> OS:ubuntu 16.04 x86-64
> I build vim from source by myself,build script is:
> ./configure \
> --with-features=huge \
> --with-compiledby="tracyone" \
> --enable-multibyte \
> --enable-gui=gtk3 \
> --enable-gpm \
2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce this are
complicated, and possibly very specific to the
On Sat, Dec 27, 2008 at 3:15 AM, Dominique Pelle wrote:
2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce
On 27/12/08 09:46, Matt Wozniski wrote:
On Sat, Dec 27, 2008 at 3:15 AM, Dominique Pelle wrote:
2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb.
You can compile your own Vim 7.2.075, see
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
I'm sure Matt is completely capable of doing this, Tony, and almost
certainly needs no assistance.
Before reporting a bug, it is always better to try reproducing it with
the latest
On 27/12/08 15:45, Ben Schmidt wrote:
You can compile your own Vim 7.2.075, see
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
I'm sure Matt is completely capable of doing this, Tony, and almost
certainly needs no assistance.
Before reporting a bug, it is always better to try
Matt Wozniski wrote:
I tried to reproduce it but I could not.
Yeah, I'm not surprised... the fact that it seems tied to a hash
table resizing makes me think that it's very much tied to the number
of plugins I have loaded, the number of variables I have defined, and
a whole bunch of other,
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce this are
complicated, and possibly very specific to the version of the runtime
files and such
Xavier de Gaye wrote:
Problem:
Vim version 7.1.298 on linux.
Vim crashes processing received netbeans messages while redrawing the
windows. This happens about once every five times when running the
[...]
The following tests have been completed successfully with
On Sun, Jun 1, 2008 at 12:05 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Xavier de Gaye wrote:
Problem:
Vim version 7.1.298 on linux.
Vim crashes processing received netbeans messages while redrawing the
windows. This happens about once every five times when running the
Xavier de Gaye wrote:
Problem:
Vim version 7.1.298 on linux.
Vim crashes processing received netbeans messages while redrawing the
windows. This happens about once every five times when running the
[...]
The following tests have been completed successfully with this
Xavier de Gaye wrote:
Problem:
Vim version 7.1.298 on linux.
Vim crashes processing received netbeans messages while redrawing the
windows. This happens about once every five times when running the
pyclewn test case described at the end of this mail. There is also
another case
Problem:
Vim version 7.1.298 on linux.
Vim crashes processing received netbeans messages while redrawing the
windows. This happens about once every five times when running the
pyclewn test case described at the end of this mail. There is also
another case where Vim crashes, with clewn
14 matches
Mail list logo
