Hi there,
I'm currently experiencing a strange behaviour.
DEFINES += QT_NO_DEBUG_OUTPUT
CONFIG += release
TARGET = myProg
TEMPLATE = app
DEFINES += QT_NO_DEBUG_OUTPUT
CONFIG += release
TARGET = myProg
TEMPLATE = app
To copy to clipboard, switch view to plain text mode
When built as realease it leads to a segmentation error on startup insight the IDE.
I switch to debug mode using modified pro file
#DEFINES += QT_NO_DEBUG_OUTPUT
#CONFIG += release
TARGET = myProg
TEMPLATE = app
#DEFINES += QT_NO_DEBUG_OUTPUT
#CONFIG += release
TARGET = myProg
TEMPLATE = app
To copy to clipboard, switch view to plain text mode
It runs fine.
sigsegv.jpg
When it occurs, it compiles and starts. On startup it runs into the error. The strange thing now is: I can press the "resume"-button, and it works. Program starts after hitting this button twice. Furthermore I can deploy the resulting *.exe and it works without any problems.
However I'm not a pro-programmer. I'm more or less coming from the "user"-side and I used Qt as a substitute for Matlab. That's why I'm not to familiar with debugging methods. I debugged algorithms and functions, observed incrementors and condition. But this seems to be beyond my horizon. Looks like it involves system-functions and -libraries. I would be glad if somebody could give me a hint on how to start finding out all about this.
I did an update to latest Qt5-version. No effect.
version.png
Thanks in advance, Lars
Bookmarks