diff options
| author | Tor Lillqvist <tlillqvist@suse.com> | 2011-09-15 11:55:35 +0300 |
|---|---|---|
| committer | Tor Lillqvist <tlillqvist@suse.com> | 2011-09-15 12:02:59 +0300 |
| commit | 6b457882d011d218ab4764e71fc8d5edfb1d8a87 (patch) | |
| tree | c9c45818703538a9408e882771e7a5f3f519578c /connectivity/source | |
| parent | c95d90199397b529de1a9979c065a7f35e52a188 (diff) | |
We can't #define _HAS_ITERATOR_DEBUGGING 0 in just some of the source files
It seems that _HAS_ITERATOR_DEBUGGING affects the layout of some
classes, which of course means horrible breakage if some of the source
files are compiled with it, the rest not.
http://msdn.microsoft.com/en-us/library/aa985939%28v=vs.80%29.aspx
http://connect.microsoft.com/VisualStudio/feedback/details/334315/has-iterator-debugging-0-causes-crash
I will just have to fix the code in this handful of source files so
that it compiles with _DEBUG defined. If I can be bothered.
Diffstat (limited to 'connectivity/source')
| -rw-r--r-- | connectivity/source/manager/mdrivermanager.cxx | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/connectivity/source/manager/mdrivermanager.cxx b/connectivity/source/manager/mdrivermanager.cxx index d9ea11e6e8d7..be2df41e1744 100644 --- a/connectivity/source/manager/mdrivermanager.cxx +++ b/connectivity/source/manager/mdrivermanager.cxx @@ -26,13 +26,6 @@ * ************************************************************************/ -#ifdef _MSC_VER -// Avoid problem due to dubious std::equal_range usage when building -// with MSVC in --enable-dbgutil mode (i.e. _DEBUG defined, using the -// debugging C/C++ runtime) -#define _HAS_ITERATOR_DEBUGGING 0 -#endif - // MARKER(update_precomp.py): autogen include statement, do not remove #include "precompiled_connectivity.hxx" |