Sorry for the late reply. I'm not yet very familiar with building the VM and did not debug it before at all 😅

As far as I can tell, everything looks fine when LoadLibrary() is called (I debugged build.win64x64/squeak.cog.spur/builddbg):

Still, these calls raise an access violation. The other attempts with 32/.dll postfixes and image path prefix fail, too. As far as I understand it, the screenshotted call should succeed because the Win32OSProcessPlugin.dll is in the same directory as Squeak.exe.

Does it matter that according to the Process Explorer, the current working directory of Squeak.exe points to the location of the image file rather than to the location of the VM? According to the docs, this should not matter?

By the way, the SSL plugin can be successfully loaded when running the same image in WSL (Ubuntu). So it's indeed a VM problem.

BTW: When trying to run a 64-bit image in a 32-bit VM (which does not work, of course), an exception is generated from the following stack:

Squeak.exe!abortMessage(char * fmt) Line 63
Squeak.exe!printUsage(int level) Line 3116
Squeak.exe!sqMain(int argc, char * * argv) Line 1636
Squeak.exe!WinMain(HINSTANCE__ * hInst, HINSTANCE__ * hPrevInstance, char * lpCmdLine, int nCmdShow) Line 1779
Squeak.exe!main(int flags, char * * cmdline, char * * inst) Line 20
Squeak.exe!__tmainCRTStartup() Line 341

Shouldn't a meaningful error window be shown here instead? Do you have any idea why this is broken? I also noticed that the args variable seems to be corrupted. Or is it just pending to be initialized properly?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.