Closed Bug 622399 Opened 14 years ago Closed 7 years ago

crashinject doesn't work on my Windows 2000

Categories

(Testing :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: sgautherie, Unassigned)

References

Details

When run from automation.py, crashinject.exe doesn't even appear in the Windows process list.

When run manually, the process appears in the list but hangs: not killing the passed pid.

I'm not sure whether this is Windows 2000 specific, nor if it could be related to bug 575917.

If it can't be fix to work, then it should just not be called on Windows 2000.
Flags: in-testsuite-
Actually, the application window does disappear, but the (Firefox) application process is still alive.

Could it be hanging in Breakpad?
Oh, maybe one of the following build options are involved:
{
--with-windows-version=502
--disable-ipc
--disable-ctypes
--disable-webm
--enable-application=browser
--enable-debug
--disable-optimize
}
I certainly don't care to make it work, you're welcome to try to avoid calling it on Win2k. Note that after Firefox 4, we're likely to explicitly unsupport Win2k, so things like this will become WONTFIX. (And in fact, I can't say I care all that much about supporting build/test scenarios on Win2k, so I'm tempted to WONTFIX this anyway.)
Windows 2000 is no longer supported.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.