On Thu, Jul 16, 2009 at 11:14 AM, Mr Moosestephan.men...@gmail.com wrote:
It is found!
After 4 interesting days of debugging the bastard I realized that I
rercently had to add 3 preprocessor defines to my build system:
_CRT_SECURE_NO_WARNINGS
_SECURE_SCL=0
_HAS_ITERATOR_DEBUGGING=0
If
OK, just for the records: Now I can be really sure. I've deleted
everything that remotely resembles a release build and changed my
build system so it won't create any and work without. And still the
bug occurs. So I don't think it is related to Microsoft runtime
issues.
Cheers,
Stephan
On 16
It is found!
After 4 interesting days of debugging the bastard I realized that I
rercently had to add 3 preprocessor defines to my build system:
_CRT_SECURE_NO_WARNINGS
_SECURE_SCL=0
_HAS_ITERATOR_DEBUGGING=0
If they are missing, many things[tm] won't work properly in debug
build. Things such
Did you make sure to compile your debug build against a debug build of
libprotobuf? MSVC fails miserably when trying to mix and match debug vs.
release, apparently because the STL classes have different representations
between the two.
On Wed, Jul 15, 2009 at 7:38 AM, Mr Moose
