STL map instance causing UMR?

[Chage]

I declared something like this and caught an UMR by using Purify.

main()
{
map<string, string> x;
exit(0);
}

below are part of the purify message:
map()
: _Mybase(key_compare(), allocator_type())
=> { // construct empty map from defaults
}

explicit map(const key_compare& _Pred)

Anyone has encountered this before? I am using VC++.Net ver7.0.9466

[Rolf Magnus]

Chage wrote:

I declared something like this and caught an UMR by using Purify.

main()
{
map<string, string> x;
exit(0);
}

The problem is not the map, but the use of the function exit(). It
doesn't call the destructors of local objects. Try just returning from
main().

[Ron Natalie]

"Rolf Magnus" <ra******@t-online.de> wrote in message news:bp*************@news.t-online.com...

Chage wrote:

I declared something like this and caught an UMR by using Purify.

main()
{
map<string, string> x;
exit(0);
}

The problem is not the map, but the use of the function exit(). It
doesn't call the destructors of local objects. Try just returning from
main().

That wouldn't have any bearing on a UMR. UMR is unitialized memory
references. Unfortunately, the entire VC++ runtime system is full
of them.