From stdcxx-dev-return-3664-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Thu Jun 07 15:34:38 2007 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 83650 invoked from network); 7 Jun 2007 15:30:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Jun 2007 15:30:30 -0000 Received: (qmail 64567 invoked by uid 500); 7 Jun 2007 15:30:34 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 64551 invoked by uid 500); 7 Jun 2007 15:30:34 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 64540 invoked by uid 99); 7 Jun 2007 15:30:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2007 08:30:33 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2007 08:30:28 -0700 Received: from qxvcexch01.ad.quovadx.com ([192.168.170.59]) by moroha.quovadx.com (8.13.6/8.13.6) with ESMTP id l57FTnRj008972 for ; Thu, 7 Jun 2007 15:29:49 GMT Received: from [10.70.3.113] ([10.70.3.113]) by qxvcexch01.ad.quovadx.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Jun 2007 09:29:05 -0600 Message-ID: <466824FB.4010507@roguewave.com> Date: Thu, 07 Jun 2007 09:32:11 -0600 From: Martin Sebor Organization: Rogue Wave Software User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: stdcxx-dev@incubator.apache.org Subject: Re: STD_BAD_ALLOC.cpp test problem on Windows References: <4666CB44.4060406@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE64388D1C99@epmsa009.minsk.epam.com> <466700AD.2090206@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE64388D1D98@epmsa009.minsk.epam.com> In-Reply-To: <7BDB2168BEAEF14C98F1901FD2DE64388D1D98@epmsa009.minsk.epam.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Jun 2007 15:29:05.0064 (UTC) FILETIME=[95307A80:01C7A918] X-Virus-Checked: Checked by ClamAV on apache.org Farid Zaripov wrote: >> -----Original Message----- >> From: Martin Sebor [mailto:sebor@roguewave.com] >> Sent: Wednesday, June 06, 2007 9:45 PM >> To: stdcxx-dev@incubator.apache.org >> Subject: Re: STD_BAD_ALLOC.cpp test problem on Windows >> >> Still, are you aware of any Windows API that lets programs >> limit the amount of dynamic memory available to them, like >> setrusage() does on UNIX? I ask because allocating so much >> storage can put a big stress on the system, even if for just >> a few seconds. > > The process memory (and/or user-mode time) can be limited using > job object, but this possibility available on Windows 2000 and later > (not available on Windows NT). That's better than nothing. Would it be pretty easy to do in the test? Martin