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 msebor@gmail.com designates
 209.85.146.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:organization:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:sender;
        b=KekfMsYD49BoAyaeG5WqhgIUgOzdQwe2u+ooaTW/8vXhXW3ACo7jtJhXk7x05j4OLF0lUGKZMmSSBAKMI0jWiwk0VoHZBoIbD9AToA5hwhVG0p+n4EKznMXwHKauIi1C0Fvsiq2ThnOdFLaF6+ef96iN850d8zwUVGIZwHA/JQs=
Message-ID: <4689CB94.8050800@roguewave.com>
Date: Mon, 02 Jul 2007 22:07:48 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.8.0.12) Gecko/20070531 Fedora/1.0.9-1.fc6 pango-text SeaMonkey/1.0.9
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: Intel C++ build issues on Windows
References: <4685352A.2020104@roguewave.com> <46854951.8000509@roguewave.com>
 <4685550B.8050503@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE64389D7445@epmsa009.minsk.epam.com>
 <7BDB2168BEAEF14C98F1901FD2DE64389D744B@epmsa009.minsk.epam.com>
In-Reply-To: <7BDB2168BEAEF14C98F1901FD2DE64389D744B@epmsa009.minsk.epam.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: Martin Sebor <msebor@gmail.com>

Farid Zaripov wrote:
>> -----Original Message-----
>> From: Farid Zaripov [mailto:Farid_Zaripov@epam.com] 
>> Sent: Monday, July 02, 2007 9:09 PM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: RE: Intel C++ build issues on Windows
>>
>>> I see. I thought we cleaned them all up. Farid, are there any more 
>>> tests or examples that you're aware of that could be causing this?
>>> I suppose it's always possible that a test will crash and pop up a 
>>> window on the screen (what a pain!) We really need to come 
>> up with a 
>>> reliable way to prevent this.
>>   There are 3 types of popup's:
>> 1) Dr.Watson window, appear on access violation or unhandled 
>> exception;
>> 2) CRT asserts and parameter validat
> 
>   I have sent unfinished message. Here the corrections:
> 
>   There are 3 types of popup's:
> 1) Dr.Watson window, appear on access violation or unhandled 
> exception;
> 2) CRT asserts ;
> 3) Parameter validattion handler popup's.
> 
>   The 1) prevented in exec utility (SetErrorMode()). The 2) and 3)
> might be prevented by installing report hook and invalid parameter
> handler:
> 
> http://www.mail-archive.com/stdcxx-dev@incubator.apache.org/msg03761.htm
> l

Gotcha! I see I still owe you a response to your feedback in that
thread. The solution in 2) and 3) will only take care of these
popups in tests and not in examples or config tests (or locales?)
We'll also need a solution for those executables (but we can worry
about that once we're done enhancing the test driver).

Martin