Re: strange crash after assertion with std::map::iterator
"Duane Hebert" <spoo@flarn2.com> wrote in message
news:uGNTOSagHHA.4552@TK2MSFTNGP04.phx.gbl
I use VS7.3 at the office but VS8 at home. I wasn't
aware of the runtime tests. I tried the code with both
iterators and pointers. With iterators, it asserts and
crashes. With pointers, it gives me two notices of
using uninitialized pointers and then shows that they
are equivalent.
They are only equivalent by accident, probably because you are running a
debug build. In debug build, compiler initializes memory occupied by
uninitialized variables to a fixed value, to help tracking down certain
bugs. That's why your two uninitialized pointers compare equal. In a
release build, they would contain random garbage, and may or may not
compare equal. You are not relying on it in your program, are you?
I guess it doesn't matter since both
are errors anyway but I guess that I thought they
should do the same thing.
Why would you ever prefer less diagnostic of error conditions over
better diagnostic? Aren't you glad the code asserts and points you to a
bug?
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925