Can't run the program
-
The built program cannot be run.
I know it's a very common question, but I can't figure it out.Because, it is a program that has been running well for several years already.
But it's not running recently.The previously built exe is operating normally.
But when I build a new one, it doesn't work.
It works fine in debug mode.No dialog, no error message, nothing.
I am using Qt version 5.15.2, and it is the same on Windows 10 and 11.
I've tried to build and run it on both sides, but it's the same.There doesn't seem to be any fixes that would cause problems with the execution itself.
I didn't change a project settings or any Qt update.
I did a windows update.Dependency checking did not appear to be particularly problematic.
Well, of course, since it was a program I kept using.Has anyone experienced a similar situation or has any doubts?
-
@HC-dev
Difficult to say. It might be genuinely "not running", or it might be "running" but you cannot see anything.It works fine in debug mode.
Do you mean when compiled for Debug or when run via Debug from Creator? Is there any difference between running it from Creator versus running it outside of Creator? If it fails from Creator, even though you may have built it for non-Debug try running it from Run versus from Debug. Any difference? If it fails from Run, still look for any messages in the output/debug panes in Creator. Does the Run terminate/exit, or does it stay running?
-
@A-A-SEZEN
When I run it, it appears briefly in the background processes side of the task manager and then disappears.
No pop-ups or messages are displayed during run and terminate.
Usually, when some dll is missing, a message is displayed or remains in a background process in the task manager,
which is a little different. because it disappears.External libraries use dcmtk, ffmpeg, opencv, zlib, and minizip, and the Qt library uses quick, qml, concurrent, sql, network, multimedia, positioning.
@JonB
It works when run in debug mode in Qt Creator. And it does work when execute exe itself outside with dlls, too.
It does not work when run in release mode in Qt Creator. And it does not work when execute exe itself with dlls, either.And... when I run the debugger, it stops.
0x7ffb4b7ea2fc <+10508> mov rax,qword ptr gs:[60h] 0x7ffb4b7ea305 <+10517> cmp byte ptr [rax+2],0 0x7ffb4b7ea309 <+10521> je ntdll!RtlRegisterSecureMemoryCacheCallback+0x292a (00007ffb`4b7ea31a) 0x7ffb4b7ea30b <+10523> mov byte ptr [ntdll!NlsAnsiCodePage+0x14c4 (00007ffb`4b858c90)],1 0x7ffb4b7ea312 <+10530> int 3 <-- HERE 0x7ffb4b7ea313 <+10531> mov byte ptr [ntdll!NlsAnsiCodePage+0x14c4 (00007ffb`4b858c90)],0
-
@HC-dev
Hi
The 5.15.2 is released in November 2020, but I believe your application is older, isn't it?
If it is so, what is the original Qt framework of your application?
If the original Qt framework is different, try to compile it with the original Qt. -
@HC-dev said in Can't run the program:
It works when run in debug mode in Qt Creator.
What output does it output in the "Application Output" tab at this time?
@HC-dev said in Can't run the program:
External libraries use ... network
Are you using an SSL connection? Are you getting TLS errors?
I think your problem might be here. -
@CP71
The program has been running for several years already, so I am using an outdated version.
The original version is 5.15.2.@A-A-SEZEN
The log when it runs is nothing special. This is the log I've always seen.
As mentioned, it has been operating for several years...I don't know why the TLS problem suddenly occurred.
If an error occurs when running in Qt Creator,FTH: (4056): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
A message appears. It is displayed when it has failed several times.
Other than that, there are no messages.
-
@hskoglund
no. It was just an answer to the use of SSL mentioned by A.A.SEZEN.
I haven't seen any messages related to the execution error. -
In the process of doing some tests, I think I got a hint.
When running in debugging mode, I found that it stopped at QFontDatabase::addApplicationFont().
It seems that this is where I stopped before in the assembly area.
ntdll!RtlRegisterSecureMemoryCacheCallback+0x292a (00007ffb`4b7ea31a) ...somethingI still don't know what caused the problem all of a sudden, but I'm glad that I seem to have found a starting point.
Thanks to everyone who responded.