Is there a significant overhead associated with calling OutputDebugString in release build?
Is there a significant overhead associated with calling OutputDebugString in release build?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a significant overhead associated with calling OutputDebugString in release build?
Measured – 10M calls take about 50 seconds. I think it’s significant overhead for unused functionality.
Using a macro can help get rid of this in release build:
Not only removes the calls, but also the parameters evaluation and the text strings are entirely removed and you’ll not see them in the binary file.