Andy Wokula wrote:
GVim7 (Win32) crashes if I do the following:
" clean startup
:new
:tabnew
:call winnr("#")
" happens with or without 219 patches included
Andy
also on Linux with gvim 7.0.219 called as "gvim -N -u NONE" and also when
replacing ":call" by ":echo".
Note that the "last ac
A.J.Mechelynck wrote:
> William S Fulton wrote:
> [...]
>> Just need spare time mate, but the SUSE guys have beat me to it already!
>> There is a buffer overrun, all the gory details here:
>>
>> https://bugzilla.novell.com/show_bug.cgi?id=182212
>>
>> It was reported as affecting vim 7 too.
>>
>> W
Hi vimmers
I have some news about the crash -- finally I found the cause.
> I don't know how to find out where the problem is. Perhaps, there
> are some resources yet occupied, or some messages in a message
> queue of some hidden windows, that leads OleUninitialize() to stop
> the whole program a
Hi vimmers
I have some news about the crash.
1) Minimal requirement to build a gvim.exe that crashes with
Microsoft Visual Studio 2005 Express Edition (VSEE):
nmake -f Make_mvc.mak FEATURES=NORMAL GUI=yes OLE=yes \
MBYTE=no IME=no GIME=no SNIFF=yes CSCOPE=no \
ICONV=no GETTEXT=no
William S Fulton wrote:
[...]
Just need spare time mate, but the SUSE guys have beat me to it already!
There is a buffer overrun, all the gory details here:
https://bugzilla.novell.com/show_bug.cgi?id=182212
It was reported as affecting vim 7 too.
William
Interesting... Notice the SuSE
Benji Fisher wrote:
> On Tue, Jun 06, 2006 at 10:27:12PM +0100, William S Fulton wrote:
>> The version of gvim shipped with Suse 10.1 crashes when using the mouse.
>> I've filed a bug: https://bugzilla.novell.com/show_bug.cgi?id=182212,
>> but here is the stack trace again (below). Any suggestions
Tony
>> But if I invoke the Taskmanager by pressing Ctrl-Alt_Delete,
>> then I observe a gvim zombie hanging around within the task
>> list.
>>
> If it doesn't happen when you build with Big features (and an
> otherwise identical configuration), then the only difference
> between Big and Hige is
Mathias Michaelis wrote:
Dear developers
I observe the following strange behaviour of gvim 7.0 on Windows XP
built with HUGE features by my own:
I open gvim.exe, work with it or leave it without touching it for
half an hour. Then, within gvim.exe, I type ":q" or ":wq". gvim
saves the text, remo
Dear developers
I observe the following strange behaviour of gvim 7.0 on Windows XP
built with HUGE features by my own:
I open gvim.exe, work with it or leave it without touching it for
half an hour. Then, within gvim.exe, I type ":q" or ":wq". gvim
saves the text, remove the .swp file and closes
On Tue, Jun 06, 2006 at 10:27:12PM +0100, William S Fulton wrote:
> The version of gvim shipped with Suse 10.1 crashes when using the mouse.
> I've filed a bug: https://bugzilla.novell.com/show_bug.cgi?id=182212,
> but here is the stack trace again (below). Any suggestions on fixing
> this would be
The version of gvim shipped with Suse 10.1 crashes when using the mouse.
I've filed a bug: https://bugzilla.novell.com/show_bug.cgi?id=182212,
but here is the stack trace again (below). Any suggestions on fixing
this would be welcome.
William
(gdb) continue
Continuing.
*** stack smashing detecte
11 matches
Mail list logo
