3 ms·
I ran into an interesting bug in 1997. My employer was developing an IDE and close to the release time we got a report from a beta tester that creating a projec
by acdha 8y ago
I ran into an interesting bug in 1997. My employer was developing an IDE and close to the release time we got a report from a beta tester that creating a project failed on a Windows 95 test box, where it would create the directory but then report that it didn’t exist!
The debug log was mystifying: the app was successfully creating the project directory but then failing to open it because the Win32 API to enumerate `C:\.` was returning an empty list and it hit the error handler when the expected directory name wasn’t in the empty list.
Naturally, we couldn’t reproduce this on any system we had access to and the customer could only reproduce it on Win95, not NT. I remembered that the Win95 networking stack was a deeply-invasive kludge and on a hunch tried disabling network file sharing, which immediately made the problem reproducible even though the local C: drive hadn’t been shared.
The IDE developer was able to side-step the big by changing the existence check to use a different API and shipped on-time. Our theory was that Microsoft’s QA team had missed the bug for the same reason we had: everything in the test environment was networked to have access to the shared builds and testcases.