4

I have a Visual Studio 2008 solution with a number of projects that all define _HAS_ITERATOR_DEBUGGING=0 in the Preprocessor Definitions setting in project files. But this only seems to work on some of the projects, while others still get compiled with iterator debugging enabled.

I have checked every file in the solution, and nowhere is _HAS_ITERATOR_DEBUGGING defined other than the project settings.

Adding #define _HAS_ITERATOR_DEBUGGING 0 to the top of each stdafx.h in the solution works around the issue, but I would like to know why setting this in the project Preprocessor Definitions section is not working some of the time. Any ideas?

Improve this question
2
  • I think Michael Burr's answer might cover it, but also note there are certain bugs when you build with _HAS_ITERATOR_DEBUGGING=0, which my company ran into because all of our software was built with that option disabled. Microsoft's compiler team mentioned it should be fixed in VS2010. Commented Nov 26, 2010 at 1:58
  • I don't like the idea of having to disable it, but in most cases this option is viral, and unfortunately one of our dependencies was build with the option disabled. Commented Nov 30, 2010 at 5:54

1 Answer 1

Reset to default
4

One thing that bites me every now and then is that project settings can easily become different between different configurations (Release vs. Debug for example). Make sure the setting is there or the configuration you're building. And of course that the define is spelled correctly...

For the projects that are having the problems, take a look at the build log (BuildLog.htm - a link to it shows up in the Build Output window) and make sure the 

-D "_HAS_ITERATOR_DEBUGGING=0"

option shows on the compiler command line (actually in the response file that has the command line options passed to the compiler).

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Checking the build log gave me the hint I needed. The problem was that Preprocessor Definitions were set at the file level for almost all of the files in the projects giving me trouble. The file level settings were set "no inherit", so the option I was setting was being ignored. The build log showed compiler options that were different than what I had set in the project settings, which led me to the answer. Thanks!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.