> -----Original Message----- > From: Farid Zaripov [mailto:[EMAIL PROTECTED] > 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 Farid.
