Crash when run in Release mode?

J.Hilk

@Mucip said in Crash when run in Release mode?:

VS 2019

MSVC is not fully supported with Qt ( 2017 is) I've run into 1 or 2 error because of that as well. Did you update/use the latest MSVC when you installed VS2019 or did you check that?

JonB

@Mucip
Forget the boxes for a second. You show the release one crashed. Did it not stop in debugger at that point and allow you to see traceback?

Mucip

@J-Hilk ,
I did not do extra things when I install VS2019. How will I update MSVC2019?

Regards,
Mucip:)

Mucip

@JonB ,
In debugger mode the debug button works well as below screenshot

Regards,
Mucip:)

Mucip

@J-Hilk
Something wrong in VS2019 I guess too :(

No solution untill now. Should I install VS2017???

Regards,
Mucip:)

Mucip

@J-Hilk ,
How can I check it please?

Regards,
Mukcip:)

Mucip

@J-Hilk ,
It's very strange!

When I build in RELEASE mode I got crash and can not run under Qt Creator!
But when I run windployqt and create executable of the project than it works without any problem!
I can connect to PostgreSQL and use LimeReport and QtZint. I mean all the DLL's work without any problem.

Project can be compiled in the release directory but can not be run via Qt... :(

Well, Where should be the problem?! I guess Qt must update something according to actual version of VS2019... :(

Regards,
Mucip:)

mzimmers

I encounter this every so often. The cause is usually what JSulm suggested -- a missing library. If your project file isn't too big, I'd be interested in looking at it.

One thing I do when I encounter this, is go to the release directory and try to run the .exe directly (outside of Creator). You'll likely get an error message telling you what's wrong (eg, which library is missing).

Mucip

Hi @mzimmers ,
If some DLL is misssing, It shouldn't be compiled. But QtCretator can compile the project.
Am I rigt?
By the way it shouldn't run in DEBUG mode either.

P.S. Thanks a lot for your kind interest. Project is liitle bit long. :)

Regards,
Mucip:)

mzimmers

@Mucip it's not that the .dll is missing - it's just not accessible to the release image. (I'm probably not the best one to explain this.) This would be a useful experiment: go into your build directory for your debug build. Find the executable and try to run it (this should work). Then go into the build directory for your release build, and do the same thing. I'm expecting you'll get an error message from the binary; if so, please post it.

Mucip

Dear @mzimmers ,
Well, I tested in DEBUG directory. Clicked MriERP.exe file. Ofcourse it says LimeReport, QtZint and QtCore and etc files are missing. When I copy these files in the debug directory I can run the program in DEBUG folder.

When I try same thing in RELEASE folder, error messages are the same. Same files are missing. I copied LimeReport, QtZint and Qt's DLL files than MriERP.exe files worked normally too.

A quick question: If some DLL are missing It shouldn't compile the project, should it?...

Regards,
Mucip:)

mzimmers

Thanks for running those tests. I misspoke when I said the debug version should run; I forgot that the libraries aren't available outside of Creator. Since you probably don't intend to run your debug version outside of Qt, that's not important.

To fix your release build, you need to do (at least) two things:

tell Creator which files (the ones you mentioned)you want to copy to your build directory. This can be done like this (in your .pro file):

my_release.files = "libexpat.lib"
my_release.path = $$OUT_PWD

INSTALLS += my_release

in your build settings, you need to add a step after make, to do a make install. This will copy the files for you.

This should not work, but might not be exactly what you want. The user can run your program out of the release directory, but if he moves the executable, it won't run. If this presents a problem, let me know, and I'll tell you how to fix this (but it will take you some time to do so).

Mucip

@mzimmers said in Crash when run in Release mode?:

my_release.files = "libexpat.lib"
my_release.path = $$OUT_PWD

INSTALLS += my_release

Hi,
How can I put two dll files in the my_release.files? Should I add path also?

By the way, what is changed after Qt 5.13.2? I didn't make this modification before? Why it happend in Qt 5.14.2?

By the way if I copy LimeReport.dll and QtZint.dll to RELEASE folder, I can run the program in Qt Creator. This mean the problem was LimeReport.dll and QtZint.dll files missing!

But why? It was working in Qt5.13.2 before???

Regards,
Mucip:)

mzimmers

@Mucip

target.path = $$OUT_PWD
target.files = "LimeReport.dll" "QtZint.dll"
INSTALLS += target

This link OUT_PWD will explain how it works.

Just make sure to add the install step to your build. Adding this stuff to the .pro files is just specifying what the install will work on.

I can't answer why it worked in 5.13.

Mucip

@mzimmers said in Crash when run in Release mode?:

target.path = $$OUT_PWD
target.files = "LimeReport.dll" "QtZint.dll"
INSTALLS += target

Hi @mzimmers,
I copied above lines in my pro file and add make step to build like below picture. But still same crash?!
I affraid I could not copy dll's to destination folder. :(
Where am I wrong?...

Regards,
Mucip:)

mzimmers

The first thing I'd check is, did the files copy over to the release directory?

I was making an assumption that you had those files available in your source directory; if not, then you need to furnish the pathnames in the .pro file.

Mucip

@mzimmers ,
No. Files did not copied in the folder. But when I add below string than everything solved. I can run program in release mode too.

target.path = $$OUT_PWD
target.files = "D:/Belgeler/Qt/LimeReport/win64/release/lib/LimeReport.dll" "D:/Belgeler/Qt/LimeReport/win64/release/lib/QtZint.dll"
INSTALLS += target

Thanks...

Regards,
Mucip:)

mzimmers

Excellent. If you like, you can create a variable in your .pro file for your directory that contains the libraries, and use that variable when specifying the target.files. Won't change the behavior; it's just a bit cleaner.

If you think this is resolved, please mark the topic as solves using the topic tools available in your first post in this thread.

Mucip

@mzimmers
I already marked your post as answer... :)

By the way there is still one question more: What is the difference between 5.13.2 and 5.14.2?... :)

Regards,
Mucip:)

SGaist

@Mucip That is something that you can find out in the release notes as well as in the git history.