hGetBuf (or something related) broken for 6.2 with sockets

Simon Marlow simonmar at microsoft.com
Mon Dec 22 07:39:37 EST 2003


> The problem with downloading things direct from CVS is that I 
> don't expect people
> to run substantial tests before checking things into CVS.  
> (We don't on our CVS
> server.)  Of course I don't expect a snapshot release to have 
> the same reliability
> as a real release, but at least snapshot releases seem to 
> compile and succeed in compiling themselves.

Well, you can always check the build reports from the nightly builds at

  http://haskell.org/pipermail/cvs-ghc/

and then check out the sources from CVS on a likely-looking date using
'cvs co -r ghc-6-2-branch -D<date>'.

> Anyway Simon, is there a workaround to the sockets problem I 
> posted or not?

hGetBuf is buggy in 6.2, thanks for bringing it to our attention.  I've
attached a working version which you can use instead of
System.IO.hGetBuf, please let me know if this helps, so we can make sure
that 6.2.1 gets it right.

Incedentally, hGetBufNonBlocking isn't right either.

Cheers,
	Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: HGetBuf.hs
Type: application/octet-stream
Size: 4816 bytes
Desc: HGetBuf.hs
Url : http://www.haskell.org/pipermail/glasgow-haskell-bugs/attachments/20031222/4d83714f/HGetBuf.obj


More information about the Glasgow-haskell-bugs mailing list