In visual studio, is there a preprocessor definition like _DEBUG for running release with debugging?
up vote
1
down vote
favorite
In Visual Studio, you can distinguish between Debug and Release modes using the _DEBUG definition. But even in release mode, you can either "Start Debugging" (F5) or "Start Without Debugging" (Ctrl + F5). Is there a preprocessor definition that distinguishes between these?
visual-studio debugging c-preprocessor
asked Nov 9 at 14:20
RandomName
266
add a comment |
up vote
1
down vote
favorite
In Visual Studio, you can distinguish between Debug and Release modes using the _DEBUG definition. But even in release mode, you can either "Start Debugging" (F5) or "Start Without Debugging" (Ctrl + F5). Is there a preprocessor definition that distinguishes between these?
visual-studio debugging c-preprocessor
asked Nov 9 at 14:20
RandomName
266
Debugging is a step after building. The system doesn't know at build time, which button the user is going to push it in the future. (What if the user does both?) Are you suggesting that pushing the debugging button should always force a rebuild, with a clue as to what the user is probably going to do next? That's not really how build configurations work.
– Raymond Chen
Nov 9 at 14:33
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
In Visual Studio, you can distinguish between Debug and Release modes using the _DEBUG definition. But even in release mode, you can either "Start Debugging" (F5) or "Start Without Debugging" (Ctrl + F5). Is there a preprocessor definition that distinguishes between these?
visual-studio debugging c-preprocessor
asked Nov 9 at 14:20
RandomName
266
In Visual Studio, you can distinguish between Debug and Release modes using the _DEBUG definition. But even in release mode, you can either "Start Debugging" (F5) or "Start Without Debugging" (Ctrl + F5). Is there a preprocessor definition that distinguishes between these?
visual-studio debugging c-preprocessor
visual-studio debugging c-preprocessor
asked Nov 9 at 14:20
RandomName
266
asked Nov 9 at 14:20
RandomName
266
asked Nov 9 at 14:20
RandomName
266
asked Nov 9 at 14:20
RandomName
266
asked Nov 9 at 14:20
RandomName
266
266
Debugging is a step after building. The system doesn't know at build time, which button the user is going to push it in the future. (What if the user does both?) Are you suggesting that pushing the debugging button should always force a rebuild, with a clue as to what the user is probably going to do next? That's not really how build configurations work.
– Raymond Chen
Nov 9 at 14:33
add a comment |
Debugging is a step after building. The system doesn't know at build time, which button the user is going to push it in the future. (What if the user does both?) Are you suggesting that pushing the debugging button should always force a rebuild, with a clue as to what the user is probably going to do next? That's not really how build configurations work.
– Raymond Chen
Nov 9 at 14:33
Debugging is a step after building. The system doesn't know at build time, which button the user is going to push it in the future. (What if the user does both?) Are you suggesting that pushing the debugging button should always force a rebuild, with a clue as to what the user is probably going to do next? That's not really how build configurations work.
– Raymond Chen
Nov 9 at 14:33
Debugging is a step after building. The system doesn't know at build time, which button the user is going to push it in the future. (What if the user does both?) Are you suggesting that pushing the debugging button should always force a rebuild, with a clue as to what the user is probably going to do next? That's not really how build configurations work.
– Raymond Chen
Nov 9 at 14:33
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Start Debugging means Start your program in the debugger.
Start Without Debugging means Start your program normally.
Since you choose one of these actions after building the program (either in Debug or
Release), there cannot be any preprocessor macro or other compiletime difference
between the actions.
The Debug build of your program can be run in the debugger, and it can be run
normally. The Release build of your program can also be run in the debugger, or
normally. But if you run the Release build in the debugger, the debugger's
ability to present the program's internal state correctly, or at all, at any
given point may be hampered for lack of valid debugging information.
It appears what you want is be able to run a Release build effectively in the debugger.
There is nothing to stop you configuring your Release build to generate
debugging information like a Debug build: it's just not the default. See How to: Debug a Release Build
This would probably be a temporary measure. While debugging a Release build in this
way, the program flow you observe might at times appear unexpected, due to Release mode optimizations.
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Start Debugging means Start your program in the debugger.
Start Without Debugging means Start your program normally.
Since you choose one of these actions after building the program (either in Debug or
Release), there cannot be any preprocessor macro or other compiletime difference
between the actions.
The Debug build of your program can be run in the debugger, and it can be run
normally. The Release build of your program can also be run in the debugger, or
normally. But if you run the Release build in the debugger, the debugger's
ability to present the program's internal state correctly, or at all, at any
given point may be hampered for lack of valid debugging information.
It appears what you want is be able to run a Release build effectively in the debugger.
There is nothing to stop you configuring your Release build to generate
debugging information like a Debug build: it's just not the default. See How to: Debug a Release Build
This would probably be a temporary measure. While debugging a Release build in this
way, the program flow you observe might at times appear unexpected, due to Release mode optimizations.
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
add a comment |
up vote
0
down vote
Start Debugging means Start your program in the debugger.
Start Without Debugging means Start your program normally.
Since you choose one of these actions after building the program (either in Debug or
Release), there cannot be any preprocessor macro or other compiletime difference
between the actions.
The Debug build of your program can be run in the debugger, and it can be run
normally. The Release build of your program can also be run in the debugger, or
normally. But if you run the Release build in the debugger, the debugger's
ability to present the program's internal state correctly, or at all, at any
given point may be hampered for lack of valid debugging information.
It appears what you want is be able to run a Release build effectively in the debugger.
There is nothing to stop you configuring your Release build to generate
debugging information like a Debug build: it's just not the default. See How to: Debug a Release Build
This would probably be a temporary measure. While debugging a Release build in this
way, the program flow you observe might at times appear unexpected, due to Release mode optimizations.
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
add a comment |
up vote
0
down vote
up vote
0
down vote
Start Debugging means Start your program in the debugger.
Start Without Debugging means Start your program normally.
Since you choose one of these actions after building the program (either in Debug or
Release), there cannot be any preprocessor macro or other compiletime difference
between the actions.
The Debug build of your program can be run in the debugger, and it can be run
normally. The Release build of your program can also be run in the debugger, or
normally. But if you run the Release build in the debugger, the debugger's
ability to present the program's internal state correctly, or at all, at any
given point may be hampered for lack of valid debugging information.
It appears what you want is be able to run a Release build effectively in the debugger.
There is nothing to stop you configuring your Release build to generate
debugging information like a Debug build: it's just not the default. See How to: Debug a Release Build
This would probably be a temporary measure. While debugging a Release build in this
way, the program flow you observe might at times appear unexpected, due to Release mode optimizations.
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
Start Debugging means Start your program in the debugger.
Start Without Debugging means Start your program normally.
Since you choose one of these actions after building the program (either in Debug or
Release), there cannot be any preprocessor macro or other compiletime difference
between the actions.
The Debug build of your program can be run in the debugger, and it can be run
normally. The Release build of your program can also be run in the debugger, or
normally. But if you run the Release build in the debugger, the debugger's
ability to present the program's internal state correctly, or at all, at any
given point may be hampered for lack of valid debugging information.
It appears what you want is be able to run a Release build effectively in the debugger.
There is nothing to stop you configuring your Release build to generate
debugging information like a Debug build: it's just not the default. See How to: Debug a Release Build
This would probably be a temporary measure. While debugging a Release build in this
way, the program flow you observe might at times appear unexpected, due to Release mode optimizations.
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
answered Nov 11 at 15:20
Mike Kinghan
29.7k762108
29.7k762108
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53227482%2fin-visual-studio-is-there-a-preprocessor-definition-like-debug-for-running-rel%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Debugging is a step after building. The system doesn't know at build time, which button the user is going to push it in the future. (What if the user does both?) Are you suggesting that pushing the debugging button should always force a rebuild, with a clue as to what the user is probably going to do next? That's not really how build configurations work.
– Raymond Chen
Nov 9 at 14:33