Windows, vim crashes when trying to load perl DLL for Strawberry Perl 5.40

[Christian J. Robinson]

Unfortunately this is beyond my ability to debug, but any time my vim binary compiled with Strawberry Perl 5.40 dynamic tries to execute a perl command, it's an instant crash. I can reproduce this on two different Windows PCs, both running Windows 11.

--

Christian J. Robinson <hep...@gmail.com>

[Heptite]

I'm giving this a bump because I'm not sure it's been seen by someone who can fix it.

[Christian Brabandt]

On Tue, 17 Dec 2024, Heptite wrote:

> I'm giving this a bump because I'm not sure it's been seen by someone who can fix it.

Ah, sorry, forgot about this. Can you run this under a debugger and
generate a stack trace?


Thanks,
Christian
--
A long memory is the most subversive idea in America.

[Christian J. Robinson]

Unfortunately it's not clear to me how to do this under Windows.

--
--
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 vim_dev+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_dev/Z2HZDyTlaU91DKw2%40256bit.org.

[Christian Brabandt]

On Tue, 17 Dec 2024, Christian J. Robinson wrote:

> Unfortunately it's not clear to me how to do this under Windows.

It depends on how you compile it. If you are using Visual Studio, it
should be possible to run the vim binary under the included debugger.
When compiling using msys2 or mingw you should be able to create a
stacktrace using gdb.

Thanks,
Christian
--
"The geeks shall inherit the earth."
-- Karl Lehenbauer

[Christian J. Robinson]

When I was able to get msys2 to compile it (without libxpm support, frustratingly) and ran it under gdb, I couldn't get it to crash. I normally compile using Cygwin's installation of mingw for cross-compiling a native Windows binary, and the only gdb provided under Cygwin doesn't seem to like that version of gvimd.exe.

--
--
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 vim_dev+u...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/vim_dev/Z2KBeoWIofNpc7%2Bl%40256bit.org.

[Heptite]

At some point this issue has been resolved. I suspect it's when Strawberry released Perl 5.42.0

[Christian Brabandt]

On Do, 14 Aug 2025, Heptite wrote:

> At some point this issue has been resolved. I suspect it's when Strawberry
> released Perl 5.42.0

That is great to hear. BTW: Is Strawberry no longer providing 32bit
builds? I just looked at
https://github.com/vim/vim-win32-installer/issues/396 and this is a
bummer for the daily Windows builds.


thanks,
Christian
--
If a person is FAMOUS in this country, they have to go on the ROAD for
MONTHS at a time and have their name misspelled on the SIDE of a
GREYHOUND SCENICRUISER!!