ghci and other test failures on Windows.

[Mike Thomas]

Hi Simon.

 > > 3.  The next step after fixing the test script issue for point 1 for
 > > the Windows regression tests will need to be the Windows compiler
 > > crashes and network hangs reported a while ago - no promises of
 > > course - the problems I expect are long standing.

 > These must have dropped off my radar - can you remind me?

I just tabulated the first twenty or so ghc compiler crashes as the test 
suite ran this evening (all of them writes to invalid locations) on 
stable branch up to date as of about midday:

finalization001.hs
hClose001.hs
hFileSize001(ghci)
hFlush001(ghci)
hGetLine001(ghci)
hGetPosn001(ghci)
hIsEOF002(ghci)
hReady001(ghci)
hSeek001(ghci)
hSeek002(ghci)
hSeek003(ghci)
hSeek004(ghci)
hSetBuffering002(ghci)
ioeGetErrorString001(ghci)
ioeGetFileName001(ghci)
ioeGetHandle001(ghci)
misc001(ghci)
openFile001(ghci)
openFile004(ghci)
openFile005(ghci)
openFile007(ghci)
readFile001(ghci)

So in fact, my assumptions based on memories of net00x test hangs in the 
past were incorrect - apologies for the misleading report.

Putting that aside however, ghci seems to be having a difficult time. 
I'll try and look further into these crashes but can't promise to get to 
it over the forthcoming week.  If we're lucky they will all be caused by 
the same problem.

Cheers

Mike Thomas.