Re: Possible buffer overflow caused by message.c:str2special(unsigned char **sp, int from) due to (wrong?) use of mb_unescape() @ message.c:1542

2012-09-18 Fir de Conversatie Bram Moolenaar
Raymond Ko wrote: After compiling VIM with Visual Studio 2012, apparently a buffer overflow was detected and caused VIM to crash. Here's my report of what I think caused it. I am using GVIM version 7.3.661 64-bit version, Windows 7, Python 2.7.x bindings, and UltiSnips plugin. GUI and

Possible buffer overflow caused by message.c:str2special(unsigned char **sp, int from) due to (wrong?) use of mb_unescape() @ message.c:1542

2012-09-17 Fir de Conversatie Raymond Ko
Hello all, After compiling VIM with Visual Studio 2012, apparently a buffer overflow was detected and caused VIM to crash. Here's my report of what I think caused it. I am using GVIM version 7.3.661 64-bit version, Windows 7, Python 2.7.x bindings, and UltiSnips plugin. GUI and MBYTE is on.

Re: Possible buffer overflow caused by message.c:str2special(unsigned char **sp, int from) due to (wrong?) use of mb_unescape() @ message.c:1542

2012-09-17 Fir de Conversatie Dominique Pellé
Raymond Ko raymond.w...@gmail.com wrote: Hello all, After compiling VIM with Visual Studio 2012, apparently a buffer overflow was detected and caused VIM to crash. ...snip... mb_unescape() seems to meant for only decoding individual characters, and stores its results inside a static local

Re: Possible buffer overflow caused by message.c:str2special(unsigned char **sp, int from) due to (wrong?) use of mb_unescape() @ message.c:1542

2012-09-17 Fir de Conversatie Raymond Ko
On Monday, September 17, 2012 6:50:08 PM UTC-4, Dominique Pelle wrote: Raymond Ko raymond.w...@gmail.com wrote: Hello all, After compiling VIM with Visual Studio 2012, apparently a buffer overflow was detected and caused VIM to crash. ...snip... mb_unescape() seems

Re: Possible buffer overflow caused by message.c:str2special(unsigned char **sp, int from) due to (wrong?) use of mb_unescape() @ message.c:1542

2012-09-17 Fir de Conversatie Ben Schmidt
On 18/09/12 8:49 AM, Dominique Pellé wrote: Raymond Ko raymond.w...@gmail.com wrote: Hello all, After compiling VIM with Visual Studio 2012, apparently a buffer overflow was detected and caused VIM to crash. ...snip... mb_unescape() seems to meant for only decoding individual characters,

Re: Possible buffer overflow caused by message.c:str2special(unsigned char **sp, int from) due to (wrong?) use of mb_unescape() @ message.c:1542

2012-09-17 Fir de Conversatie Ben Schmidt
On 18/09/12 10:30 AM, Ben Schmidt wrote: On 18/09/12 8:49 AM, Dominique Pellé wrote: Raymond Ko raymond.w...@gmail.com wrote: Hello all, After compiling VIM with Visual Studio 2012, apparently a buffer overflow was detected and caused VIM to crash. ...snip... mb_unescape() seems to meant

Re: Possible buffer overflow caused by message.c:str2special(unsigned char **sp, int from) due to (wrong?) use of mb_unescape() @ message.c:1542

2012-09-17 Fir de Conversatie Ben Schmidt
Here are the steps: 1. Get Visual Studio 2012. The Express edition should be using the same compiler for the backend but I'm not sure. 2. Compile VIM. Not that the default Make_mvc.mak file doesn't work anymore because the Windows SDK is no longer referenced by the vcvarsall.bat. Instead I had to