- This topic has 1 reply, 2 voices, and was last updated 39 minutes ago by
.
-
Posts
-
I am debugging under Linux and have a program that exits very early in its initialization. VisualGDB reports that gdbserver has exited because the program has exited with a return code of 129.
How do I configure VisualGDB to only deploy the program but do not run it?
Hi,
If you are only trying to troubleshoot the initialization error, you should normally not need this. Once you press F5, VisualGDB deploys the program and attempts running it. Once it exits with code 129, it still remains deployed as if the debugging was never launched. So, you can run it manually and see what is going on (most likely some dynamic libraries are missing).
If you are trying to do something else, please let us know more about what you are trying to accomplish, so we could suggest the best way to do it.
- You must be logged in to reply to this topic.