__cxa_throw _bad array_ new_length not found in the dynamic link library C:\Users\Asma\Documents\Ckconvert\release\Qt5Core.dll
-
Hello guys,
I'm running Qt creator with 2 different kits :Qt 5.3.0 mingw482_32.
Qt 5.6.0 mingw492_32.i made my app and build it with Qt 5.6.0 mingw492_32 , and now i want to deploy it, i tried to run my .exe from release file but always same problem, i searched this problem in google and tried different solutions ( add platforms next to my .exe , i added LibEGL.dll and libEGLd.dll too ) but always same problem, this is my realse file
This is the error i get when i try to open my .exe ( release mode )
this error is written in french, this is the translation :
Title : ckconvert.exe - entry point not found
the procedure entry point
__cxa_throw bad array new_length not found in the dynamic link library C:\Users\Asma\Documents\Ckconvert\release\Qt5Core.dllI think my problem is coming because i have two versions of kit ( the 5.3.0 is the oldest one ) and maybe the OS is looking for the wrong Qt5Core.dll despite that i have put the good one ( from Qt5.6.0 ) ?
Can i get Help ? Thanks@Zunneh hi
do not copy and past stuff by hand, use the Windows deployment tool
https://doc.qt.io/qt-5/windows-deployment.htmleach compiled (Qt)lib has one, so make sure to use the one from the 5.6.0 director (the build version)
-
@Zunneh hi
do not copy and past stuff by hand, use the Windows deployment tool
https://doc.qt.io/qt-5/windows-deployment.htmleach compiled (Qt)lib has one, so make sure to use the one from the 5.6.0 director (the build version)
wrote on 2 Mar 2020, 13:12 last edited by@J-Hilk
Hi,
thanks for your answer, i tried windeployqt and this is the result when i try to run
it seems like windeploy Qt forget to add libwinpthread-1.dll, i added this file manually ( copy and paste ) and i still get the same problem
Same problem...
-
@J-Hilk
Hi,
thanks for your answer, i tried windeployqt and this is the result when i try to runit seems like windeploy Qt forget to add libwinpthread-1.dll, i added this file manually ( copy and paste ) and i still get the same problem
Same problem...
@Zunneh did you remove the previously copied dlls beforehand ?
And did you use the correct windeployqt ? (I have to ask 🙈)From the console command, I can see it matches with the version you said, was used for the program
-
@Zunneh did you remove the previously copied dlls beforehand ?
And did you use the correct windeployqt ? (I have to ask 🙈)From the console command, I can see it matches with the version you said, was used for the program
wrote on 2 Mar 2020, 13:17 last edited by@J-Hilk yeah of course i removed the all dll before doing windeployQt ( i deleted all the content of release file then build it again )
about the good version :
-
@J-Hilk yeah of course i removed the all dll before doing windeployQt ( i deleted all the content of release file then build it again )
about the good version :
@Zunneh 🤔
do you have Qt Libs in your system path variable ? -
wrote on 2 Mar 2020, 13:20 last edited by
@J-Hilk
-
wrote on 2 Mar 2020, 15:35 last edited by
Hi, it's a bit odd that your libwinpthread-1.dll is not from the same year as the other 2 MinGW dlls (libgcc_s_dw2-1.dll and libstdc++-6.dll).
I've deployed lots of Qt MinGW installations, and every time I've seen that those 3 dlls: libwinpthread-1.dll, libgcc_s_dw2-1.dll and libstdc++-6.dll are from the same year, month and day (even the hour and minutes are the same).
Maybe you can find a libwinpthread-1.dll that has the date summer of 2018 and not from december 2014. -
Hi, it's a bit odd that your libwinpthread-1.dll is not from the same year as the other 2 MinGW dlls (libgcc_s_dw2-1.dll and libstdc++-6.dll).
I've deployed lots of Qt MinGW installations, and every time I've seen that those 3 dlls: libwinpthread-1.dll, libgcc_s_dw2-1.dll and libstdc++-6.dll are from the same year, month and day (even the hour and minutes are the same).
Maybe you can find a libwinpthread-1.dll that has the date summer of 2018 and not from december 2014.wrote on 2 Mar 2020, 19:44 last edited by@hskoglund how can i find it ? its not easy...
-
wrote on 2 Mar 2020, 19:57 last edited by
Hi, libgcc_s_dw2-1.dll and libstdc++-6.dll are already on your computer, so try looking for all instances of libwinpthread-1.dll on your computer, open a CMD window and type:
dir C:\libwinpthread-1.dll /a/s -
Hi, libgcc_s_dw2-1.dll and libstdc++-6.dll are already on your computer, so try looking for all instances of libwinpthread-1.dll on your computer, open a CMD window and type:
dir C:\libwinpthread-1.dll /a/swrote on 3 Mar 2020, 13:01 last edited by@hskoglund No one was found with the same Date, i will try to Deploy with another version.
I have a question, if i deploy without the possibility to open my .exe in release, it will work ? -
wrote on 3 Mar 2020, 13:21 last edited by
No, if double-clicking on the .exe does not start your application ok, then deploying would be just a waste of time.
One other possibility to get a good copy of libwinpthread-1.dll, you could try installing a newer version of Qt for the MinGW compiler, like the current one, it's 5.14.1.
-
No, if double-clicking on the .exe does not start your application ok, then deploying would be just a waste of time.
One other possibility to get a good copy of libwinpthread-1.dll, you could try installing a newer version of Qt for the MinGW compiler, like the current one, it's 5.14.1.
wrote on 3 Mar 2020, 16:21 last edited by Zunneh 3 Mar 2020, 16:25@hskoglund
I made it finally, guess what i have done ? i changed the libstdc++-6.dll and libgcc_s_dw2-1.dll files to make the three files ( libstdc++-6.dll and libgcc_s_dw2-1.dll and libwinpthread-1.dll ) with the same date ( from 2014 ) and now it work perfectly, thanks for your Help
i don't know why but when i deployed the date of libstdc++-6.dll and libgcc_s_dw2-1.dll have changed ( or maybe he taked the wrong one )
11/13