- This topic has 1 reply, 2 voices, and was last updated 11 years, 10 months ago by
.
-
Posts
-
How can I keep the shell that pops open during deployment/debugging alive and present in visual studio even after the debug session is finished.
In many cases you are not setting a breakpoint and you want to just run your app and see the output. As it is, the shell opens, app runs quick, shell closes…even if I put a scanf or cin>>, the shell still does not seem to stay open.
Is there any way to have it remain open or, at the very least, remain open after an execution until you press a key or dismiss it? VS does this when you compile win32 console applications…when you run them from the IDE, they pause after they are executed and you see “press any key to continue” or something like that before the IDE closes the dos/shell window.
Is something like that possible?
Hi,
Currently this is not possible directly. You can put a breakpoint at the end of the main() function to achieve a similar result.
Using scanf() or cin should normally work. Please send us an archive with an entire test project (including the source code and the Visual Studio project files). If this is a bug of VisualGDB, this will help us to reproduce and fix it.
- You must be logged in to reply to this topic.