GNOME Bugzilla – Bug 756922
Missing entry point „__gxx_personality_sj0“ in „libstdc++6.dll“ (Startup messages of standard plugins after Windows extension pack)
Last modified: 2018-05-24 15:47:32 UTC
Details: System: W-XP SP3 V 5.1 Build 2600.xpsp_sp3_qfe.130704-0421: SP3 Special patched for industrial software, but not related to core or graphics. Product: GIMP First running installation: gimp-2.8.14-setup-1.exe (german installation installed into a new dir with a user defined path, diffent to the former dir of gimp 2.6.), GIMP_Extensions_v2.8.20150403.exe, gimp-help-2-2.8.1-de-setup.exe. During first starting up Help-Browser.exe was warning 3 times during installation: Procedure entry point „__gxx_personality_sj0“ not found in DLL „libstdc++6.dll“ In German: Der Prozedureinsprungpunkt „__gxx_personality_sj0“ wurde in der DLL „libstdc++6.dll“ nicht gefunden.
Amendment: The 3 messages had not been given by the help-browser.exe alone. During each start up of my GIMP now these messages are given from: webpage.exe help-browser.exe file-pdf-load.exe And yesterday the help browser had not been accessable. So this entry point seem to miss in one of my dll's. There are two versions of libstdc++-6.dll under my GIMP 2.8: The first is in directory .\bin (Size 828 KB 25.08.2014 19:19) and the second is in .\lib\gimp\2.0\plug-ins (Size 1003 kB 16.03.2015 12:27) I will try to change the first and hope that is it. If that's not working, I can not exclude, that the problem is coming from an other site, where an other version of libstdc++-6.dll is located in an directory, which might be linked in for system uses. I have some more libstdc++-6.dll on my PC. I'll see. I've found a similar problem explained in the Q-Forum: https://forum.qt.io/topic/39804/procedure-entry-point-libstdc-6-dll N.M.
It seems to be a problem only of the plug-in installation of file-pdf-load.exe help-browser.exe webpage.exe for a Windows XP 32-System. First I've removed the libstdc++-6.dll, which had been located in an directory, which might be linked in for system uses. Then I've checked the entry points of the two versions of libstdc++-6.dll under my GIMP 2.8: The shorter not the longer is containing the missing entry-point. The libstdc++-6.dll with the size 1003 kB has instead of the missing entry point an entry point "__gxx_personality_V0", from which I assume to be equivalent.
There should be no DLL files in the plug-ins directory. If I got comment #2 right, you have found that the DLL file in GIMP's bin directory does provide that entry point - and this is the file that is provided by GIMP installers. I'd suspect the GIMP_Extensions_v2.8.20150403.exe to have provided the DLL causing trouble. A possible workaround is to make sure the contents of this package are not placed into GIMP's default plug-ins directory, but into a new one you'll create.
(In reply to Michael Schumacher from comment #3) > There should be no DLL files in the plug-ins directory. WORK_AROUND. OK I've deinstalled GIMP_Extensions_v2.8.20150403.exe and the .dll are away from there. The three disturbed plugins are part of the standard-installations. So I recommend to unable this kind of conflicts by protecting this and other sensitive pathes or by precautions (f. ex. prioriting schemes) in the standard packs. Therefore I have shift this from component "Windows installer" to "Plugins" and will open a new "General" file. > If I got comment #2 > right, you have found that the DLL file in GIMP's bin directory does provide > that entry point - and this is the file that is provided by GIMP installers. That is. > I'd suspect the GIMP_Extensions_v2.8.20150403.exe to have provided the DLL > causing trouble. Yes, I have identified "GIMP Extensions Pack for Windows" as the offender. > A possible workaround is to make sure the contents of this > package are not placed into GIMP's default plug-ins directory, but into a > new one you'll create. There is no box during the installing process for doing so. So I've tried first to unpack the .exe and found out that there is used a bad kind of practice: There are a lot of double file names (including extensions) in the lib-subdirectory. So that may be no easy job. So I've reinstalled the Extension Pack with "plug-ins" deselected and till now I couldn't find such a conflict. Today I only need the additional file types of that package and so I will install the missing plugins later on by need. When I can find out interesting details, I will announce. N.M.
Created attachment 351972 [details] libstdc++-6.dll error on application startup At start up of GIMP 2.8.20 and GIMP 2.8.22 an error message about libstdc++-6.dll show up three times. The error message is in Swedish, since that is my native language. Since it occured in 2.8.20 I thought that upgrading to 2.8.22 would slove the problem, but it didn't. GIMP starts though, and I don't know what might not work because of this error. / Hans Gatu
And it is the same issue as described in this bug report? The previous comment explain what is going on, please let us know if you need help to figure out what you can do.
+1 but with different dll's during startup: web-page.exe: The procedure entry point _ZdlPvy could not be located in the dynamic link library C:\Program Files\GIMP 2\bin\libwebkitgtk-1.0-0.dll. help-browser.exe: The procedure entry point _ZdlPvy could not be located in the dynamic link library C:\Program Files\GIMP 2\bin\libwebkitgtk-1.0-0.dll. file-pdf-load.exe: The procedure entry point _ZdlPvy could not be located in the dynamic link library C:\Program Files\GIMP 2\bin\libpoppler-glib-8.dll. Errors occur since v2.8.20. Cheers Harald
*** Bug 782537 has been marked as a duplicate of this bug. ***
Does this still happen on the latest 2.8 installer?
-- 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/783.