When closing application Exception Triggered.
-
@JonB , I modified main.cpp to:
#include <QApplication> //Add this #include "main window.h" //#include "trainer.h" int main(int argc, char* argv[]) { //Trainer trainer(argc, argv); QApplication a(argc, argv); MainWindow w; w.show(); return a.exec(); //return trainer.exec(); }Rebuilt and it does exactly the same, crash location is in exactly the same place.
@SPlatten
Remove#include "main window.h"and replaceMainWindow w;byQMainWindow w;(with presumably#include <QMainWindow>).If that does not work, since it is the minimal Qt application what has changed for you since you last successfully built/ran any Qt GUI program?
-
@SPlatten
Remove#include "main window.h"and replaceMainWindow w;byQMainWindow w;(with presumably#include <QMainWindow>).If that does not work, since it is the minimal Qt application what has changed for you since you last successfully built/ran any Qt GUI program?
@JonB , to be honest, it could be the build of the laptop, its an older version of Qt:
Qt Creator 4.4.1 Based on Qt 5.9.2 (MSVC 2015, 32 bit)I have no control over the laptop or the version of Qt being used, this is supplied by the company I am contracted to.
-
@SPlatten well, in the stack trace, what's the first entry, thats from your code ?
you know that you can step back, when you're in assembler code right?
-
@J-Hilk , I've expanded the stack trace and there is no call the traces back to my source, the first call is in Function: RtlGetAppContainerNamedObjectPath, File: ntdll
@SPlatten thats unfortunate
since this is a basic and small project so far, can you share, the minimal example ?
that means probably only your custom MainWindow, so we can check ourselves, and check it against different Qt versions as well
Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct
Q: What's that?
A: It's blue light.
Q: What does it do?
A: It turns blue. -
@SPlatten thats unfortunate
since this is a basic and small project so far, can you share, the minimal example ?
that means probably only your custom MainWindow, so we can check ourselves, and check it against different Qt versions as well
@J-Hilk
That is why I suggested @SPlatten should useQMainWindow, not his ownMainWindow, to test. If that still does not work (I'm not sure if he has answered that), then something is fundamentally with his Qt/environment. I would do that before examining anything about a customMainWindowor header file. -
@SPlatten thats unfortunate
since this is a basic and small project so far, can you share, the minimal example ?
that means probably only your custom MainWindow, so we can check ourselves, and check it against different Qt versions as well
@J-Hilk , in doing this, I decided to go one better. I did the following in Qt Creator:
- Clicked on File top line menu
- Selected New File or Project...
- Selected Application and Qt Widgets Application
- Clicked on the Choose... button
- Entered test into Name: text box and clicked the Next button
- Checked only Desktop Qt 5.9.2 MSVC2015 32bit in Kit Selection
- Clicked Next button
- Clicked Next button
- Clicked Finish button
- Right clicked project and selected Rebuild
- Run application in debug mode and clicked the close widget in the MainWindow
Same thing happens, application stops and Exception Triggered dialog is displayed.
Kind Regards,
Sy -
@J-Hilk , in doing this, I decided to go one better. I did the following in Qt Creator:
- Clicked on File top line menu
- Selected New File or Project...
- Selected Application and Qt Widgets Application
- Clicked on the Choose... button
- Entered test into Name: text box and clicked the Next button
- Checked only Desktop Qt 5.9.2 MSVC2015 32bit in Kit Selection
- Clicked Next button
- Clicked Next button
- Clicked Finish button
- Right clicked project and selected Rebuild
- Run application in debug mode and clicked the close widget in the MainWindow
Same thing happens, application stops and Exception Triggered dialog is displayed.
-
@SPlatten Is it a 32bit bug? Try to make a 64bit build to see if you have the same problem.
-
@JoeCFD , thank you, thats a shame, the problem is the target is 32 bit so regardless of if it works in 64 bit, thats not an option.
-
@SPlatten That is unlucky. Install a 32 bit debug build of Qt 5.9.2 and debug into qt code to see the cause.
