Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of Farid_Zaripov@epam.com
 designates 217.21.63.3 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: STD_BAD_ALLOC.cpp test problem on Windows
Date: Wed, 6 Jun 2007 21:32:39 +0300
Message-ID: <7BDB2168BEAEF14C98F1901FD2DE64388D1C99@epmsa009.minsk.epam.com>
In-Reply-To: <4666CB44.4060406@roguewave.com>
Thread-Topic: STD_BAD_ALLOC.cpp test problem on Windows
Thread-Index: AceoSs82nGKiJi4PT1WiNAFm2gJexwADb2Xg
References: <4666CB44.4060406@roguewave.com>
From: "Farid Zaripov" <Farid_Zaripov@epam.com>
To: <stdcxx-dev@incubator.apache.org>

> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]=20
> Sent: Wednesday, June 06, 2007 5:57 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: STD_BAD_ALLOC.cpp test problem on Windows
>=20
> Hi Farid,
>=20
> In case you haven't seen this yet (I just noticed it for the=20
> first time myself), the STD_BAD_ALLOC.cpp has caused an ERROR=20
> in one of our MSVC builds on Windows. Do you see an easy way=20
> to prevent it from sucking up all the available memory on=20
> Windows like we do on UNIX via setrlimit()?
>=20
> http://people.apache.org/~sebor/stdcxx/results/windows-2003-em
> 64t-msvc-64b-8.0-15s-log.gz.txt

  There new() called with (unsigned long)(-1) which is 0xffffffff on
Windows 32 and Windows 64.
If the workstation have 4 Gb of memory (including virtual) the memory
allocation may be successful
and take long time.

  Possible that (http://svn.apache.org/viewvc?view=3Drev&rev=3D544910) =
would
help...

Farid.