2009/3/31 Kristján Valur Jónsson <krist...@ccpgames.com>: > Right, my question to microsoft was more about making sure that a > __crtMessageBox() actually does nothing, when running unattended as a service. > > Also, we should be seeing the same problem in non-debug versions, since the > _set_invalid_parameter_handler() is no longer called, and the default one > also puts up a message box. The Assertion is then performed _in_addition_ on > debug builds: > >From > >ms-help://MS.VSCC.v80/MS.MSDN.v80/MS.VisualStudio.v80.en/dv_vccrt/html/c0e67934-1a41-4016-ad8e-972828f3ac11.htm > In the following example, an invalid parameter error handler is used to print > the function that received the invalid parameter and the file and line in CRT > sources. When the debug CRT library is used, invalid parameter errors also > throw an assertion, which is disabled in this example using _CrtSetReportMode. > > Btw, I am working on finding out the test suite failures for > test_multiprocessing. > K
I spoke to Martin about this yesterday, apparently a specific test in the multiprocessing suite was triggering these dialogs (the test invalid handle test). We're working on a patch for multiprocessing so that the children will obey the flag -jesse _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
