This appears since v8.1.2092 with call system('which msvcrt-ruby260.dll')
in _vimrc.
Here is gdb output:
(gdb) run
Starting program: D:\Logiciels\Vim\vim81\gvimd.exe
[New Thread 5208.0x248c]
[New Thread 5208.0x186c]
[New Thread 5208.0x24f4]
warning:
mincore\com\oleaut32\typelib\tlibapi.cpp(2279)\OLEAUT32.dll!75325116:
(caller: 75324EB5) ReturnHr(1) tid(d54) 8002801D Biblioth▒que non inscrite.
Thread 1 received signal SIGSEGV, Segmentation fault.
0x77696cb3 in *strcat *() from C:\WINDOWS\System32\msvcrt.dll
Le mardi 1 octobre 2019 03:17:36 UTC+2, Ken Takata a écrit :
>
> Hi,
>
> 2019/9/30 Mon 20:55:28 UTC+9 Ni Va wrote:
>>
>> Found that this command call system('which msvcrt-ruby260.dll') causes
>> segfault under windows, which does not exist.
>> Surprised that it causes segfault.
>>
>> Thank you.
>>
>
> Can you bisect which version causes this issue?
> If you want to get more detail information on gdb, try adding the -g
> option to CFLAGS by editing Make_cyg_ming.mak.
>
> Regards,
> Ken Takata
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/e57e8bc5-1a51-4056-a842-ef7b84b35ad1%40googlegroups.com.
