On Fri, Jul 18, 2008 at 4:14 AM, Thomas Heller <theller at ctypes.org> wrote: > The most annoying thing on the windows buildbots is when Python crashes hard > (with a general protection fault or stack overflow, for example). > Usually the system pops up a dialog in this case which allows to > attach a debugger to the process. This dialog will stay open until > the maintainer manually closes it, and will prevent the next builds. > > On my boxes I have inserted these two lines into the PythonXY/Scripts/buildbot > script, right at the top: > > import win32api; win32api.SetErrorMode(7) > print "SetErrorMode(7) called." > > These lines prevent the dialog box to be displayed for critical errors. > > For example, on Windows AMD64 the test_cpickle test in the trunk currently fails with > a stack overflow; instead of hanging with the mentioned dialog box open the test now terminates: > > http://www.python.org/dev/buildbot/trunk/amd64%20XP%20trunk/builds/40/step-test/0 That's a great trick! I seem to remember that there is a way to turn that off globally though, but not sure where. Maybe running drwtsn32.exe and un-checking 'Visual Notification' does the trick? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4