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.
Le lundi 30 septembre 2019 13:28:36 UTC+2, Christian Brabandt a écrit :
>
>
> On Mo, 30 Sep 2019, Ni Va wrote:
>
> > Hi,
> >
> >
> > Since same compilation under windows 10 MSYS2 32bits to build , I got a
> seg
> > fault on gvim launch.
> > Sorry but gdb didn't tell me exact source.
> >
> > Thank you in advance.
>
> try starting without any configuration files to rule plugins and
> settings out. Also, try starting gvim.exe with -f so it doesn't fork.
>
> Does it also happen with vim.exe?
>
>
>
> Best,
> Christian
> --
> Affe:
> ein Tier, das auf Bäumen lebt, besonders gern auf Stammbäumen.
>
--
--
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/3c109767-3cc9-4a14-aafd-9151b3f6a4b4%40googlegroups.com.
