GNOME Bugzilla – Bug 795386
2.10rc1 fails to run on Windows Vista
Last modified: 2018-05-24 19:31:31 UTC
Error dialog at startup: Title: gimp-2.10.exe - entry point not found Message: Entry point to SymSetScopeFromAddr procedure not found in dbghelp.dll library. Further info is: Event issue name: APPCRASH App name: gimp-2.10.exe App version: 2.10.0.0 Ap[p timestamp: 5aba762a Error module name: dbghelp.dll!SymSetScopeFromAddr Error module version: 6.0.6002.19623 Error module timestamp: 56ec4641 Exception code: c0000139 Exception offset: 00000000000b7e68 OS version: 6.0.6002.2.2.0.256.6 Language code: 1058 Additional data 1: fa3e Additional data 2: ac0507478d1c5bd693cfc4fe3987e900 Additional data 3: fa3e Additional data 4: ac0507478d1c5bd693cfc4fe3987e900
It was suggested that this was because of the debug dialog. As said on IRC, I can see some references to SymSetScopeFromAddr in drmingw. But it's in def files not in source code (I'm a bit fuzzy what these def files are for). So I guess maybe if drmingw uses this, that would be a reason (according to Microsoft docs, this function appeared in DbgHelp.dll 6.8 (no idea which version Vista had, but most likely an older one then). It means that the fix has to be done in drmingw, or else that we must not build with drmingw support for Vista. This all being said, since we don't support Windows Vista officially (cf. devel-docs/os-support.txt in the tree), because Microsoft itself stopped supporting since April 11, 2017 (https://support.microsoft.com/en-us/help/22882/windows-vista-end-of-support), I don't think the effort is worth it. If there was a very easy solution, why not. But I don't see one, unless we just don't build at all with drmingw support, but really this would be a bit sad to lose the debug feature (even though arguably, drmingw traces are not as useful as gdb or lldb traces, they are still better than nothing). Ell > since you are the packager for Windows, what do you think? Do you think you should drop drmingw if it breaks GIMP for Windows Vista (which we don't support officially)? I'd vote no, but I don't mind if you or someone else really wants to keep maximum compatibility even on unsupported platforms.
The last release of Vista was 2009, I vote for dropping support.
(In reply to Michael Natterer from comment #2) > The last release of Vista was 2009, I vote for dropping support. Officially we already dropped support since our support is Windows 7 and over. Cf. file `devel-docs/os-support.txt` in the repository. :-)
Ok so let's put it a WONTFIX, because it is happening on an unsupported platform.
Actually, it looks like this DLL is designed to be redistributable, so this should be fixable by simply bundling the correct version with the installer.
Ell > since you are the one making the actual work on this one, you make the calls. :-) Feel free to reopen the report if you want to improve the situation by bundling the DLL.
I've added the necessary DLLs to the build, so this should be fixed in the next installer. Not sure if this is enough for GIMP to run on XP/Vista, but at least this specific problem should be fixed.
Does the current 2.10.0 still work on Vista?
Reopening to get a definitive answer on that :)
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1368.