Qt Creator launch: app not closing and/or "Press <RETURN> to close this window..." missing
-
Back to the topic after the winter break.
I've reinstalled a fresh Qt develop environent on Windows. Awfully, the behavior is still the same. With MSVC compiler (and debugger), no "Press <RETURN> to close this window..." line.
I've noticed that with MinGW I get the "Press <RETURN> to close this window..." line.Given the fact that MinGW is behaving as expected, the fact that the previous test on Linux worked was due to the compiler/debugger more than the Qt version (MinGW is a "Windowized g++")
I suppose that the "CDB Debugger Support" componet installed with the new versions of Qt is screwing some things, and the "Press <RETURN> to close this window..." line won't be displayed no more.Is there anyone that can confirm this behavior?
And anyone else that knows how to fix it? :) -
Hi
Not sure if we think about the same command prompt, but ill just mentioned it anyway
Try flipflop it.
-
Yep, I'm talking about that command promt.
The "Run in terminal" checkbox is checked. No better result by unchecking/rechecking/whatever.
From your screenshot, it looks like you are using the last version of Qt libraries (Qt 5.10.0), but an old version of Qt Creator, am I right? As said in my first messages, with older version of Qt Creator (and Qt libs) everything behaved as expected.
If someone can kindly test the last release of Qt+Qt Creator with MSVC compiler/debugger and report their results I'll be very thankful! -
Yep, I'm talking about that command promt.
The "Run in terminal" checkbox is checked. No better result by unchecking/rechecking/whatever.
From your screenshot, it looks like you are using the last version of Qt libraries (Qt 5.10.0), but an old version of Qt Creator, am I right? As said in my first messages, with older version of Qt Creator (and Qt libs) everything behaved as expected.
If someone can kindly test the last release of Qt+Qt Creator with MSVC compiler/debugger and report their results I'll be very thankful!@massimo.cristofolini
Hi
its the Creator that comes with
Qt5.10. Im just using the classic theme.
Ill check exact version when possible. -
Fooled by the picture.
Uhm... so it actually looks like I'm the only unlucky guy that's experiencing this behavior.
Another test I can make is to install the last version of Qt on a clean Windows system. Will take a while... -
Fooled by the picture.
Uhm... so it actually looks like I'm the only unlucky guy that's experiencing this behavior.
Another test I can make is to install the last version of Qt on a clean Windows system. Will take a while...Hi
If it works with mingw compiler, then it sounds like something with VS compiler ? -
@mrjj I agree. But since I've started experiencing this behavior just after Qt upgrade, on 2 systems, I have to say that both MSVC and Qt have something to do with it.
-
Hi
Im on Creator 5.10 with vs 2015
Maybe delete .user file and set compiler again ?
Or test with default empty project and set Run in terminal. -
As said in the first post, this happens with the default and almost-default console project.
Tried to delete .user file of an existing project: no luck.
Tried creating a new project again: still no luck. -
As said in the first post, this happens with the default and almost-default console project.
Tried to delete .user file of an existing project: no luck.
Tried creating a new project again: still no luck.Ok. i really dont know how it can "fall off"
I have not heard about this before.it DOES run the qcreator_process_stub.exe ?
(as seen in my image - caption) -
Ok. i really dont know how it can "fall off"
I have not heard about this before.it DOES run the qcreator_process_stub.exe ?
(as seen in my image - caption)@mrjj Now THAT was the right question!
Running a MinGW project opens the executable in qcreator_process_stub.exe.
Running from a MSVC runs the actual executable (the window title is the executable full path).
The Run Settings for both configurations (MinGW and MSVC (x86 and x64)) looks identical to me; both have "Run in terminal" checked, ... Maybe I have to look in the Run Environment section, since both are set to "use Build Environment", but maybe the environment variables differ for the two configrurations.
Any other hint about where to look at? -
@mrjj Now THAT was the right question!
Running a MinGW project opens the executable in qcreator_process_stub.exe.
Running from a MSVC runs the actual executable (the window title is the executable full path).
The Run Settings for both configurations (MinGW and MSVC (x86 and x64)) looks identical to me; both have "Run in terminal" checked, ... Maybe I have to look in the Run Environment section, since both are set to "use Build Environment", but maybe the environment variables differ for the two configrurations.
Any other hint about where to look at?Hi. i didnt find anything else to check with this.
I find it odd if u delete .user file and select compiler how
"run in terminal" can do differently. very odd. -
Hi. i didnt find anything else to check with this.
I find it odd if u delete .user file and select compiler how
"run in terminal" can do differently. very odd.@mrjj said:
Hi. i didnt find anything else to check with this.
I find it odd if u delete .user file and select compiler how
"run in terminal" can do differently. very odd.Very odd could mean it's a bug. I didn't find something like this problem in the bug database yet.
@massimo-cristofolini: So you could report this issue at bugreports.qt.io
-
