416597 - qm-win2k3-01 hanging with a "choose debugger" dialog up

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Phil Ringnalda (:philor)]

Three times in the last three days, for 10 hours, 2 hours (because stuart was watching it), and 5 hours, our only Windows unit test box has been hung with the Visual Studio debugger selector dialog up - from bug 416512:

[[[
Jeremy Orem   2008-02-09 00:33:09 PST

Box rebooted and slave started.

One observation, every time this box is stuck a Visual Studio debugger selector
is always in the foreground.

Ted Mielczarek (:luser)  2008-02-09 06:20:08 PST

We could disable that per:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconenablingjit-attachdebugging.asp

Under the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current
Version\AeDebug, set "Auto"=0
]]]

Comment 1

[(not currently active) Ted Mielczarek]

cc'ing robcee

Comment 2

[Chris Cooper [:coop] (he/him)]

This is actually in he instructions for setting up these boxes (http://wiki.mozilla.org/BuildbotTestfarm), which is why I thought this was defacto. Turns out those wiki instructions are wrong: they suggest setting the "Debugger" to an empty string rather than Auto=0.

Given that, this change probably needs to be made on all the Windows buildbot slaves.

Comment 3

[Chris Cooper [:coop] (he/him)]

I've updated the docs at http://wiki.mozilla.org/BuildbotTestfarm and I've disabled debugging on the following machines:

* qm-winxp01
* qm-stage-winxp01
* qm-leak-winxp01
* qm-win2k3-01
* qm-leak-w2k3-01

Not sure if talos machines are affected by this or not, but I don't have access to them anyway.

Comment 4

[Rob Campbell [:rc] (:robcee)]

they wouldn't be since they don't have any development tools installed on them.

thanks coop!