There's something very suspicious here, but it might be a
bug we know about.
Did you build ghc yourself, from sources? Did you
bootstrap using itself? And finally, exactly what
version of gcc do you have?
J
| -Original Message-
| From: Pixel [mailto:[EMAIL PROTECTED]]
| Sent:
According to the GHC libraries manual, 6.2.1: The Handle
returned by connectTo and
accept is unbuffered by default. However, with such a
handle and hPutStrLn,
I am getting buffering, even when use IO.hSetBuffering to
NoBuffering. When I
put in an explicit hFlush after the
Julian Seward (Intl Vendor) [EMAIL PROTECTED] writes:
% ghci
[...]
Loading package std ... linking ...
/usr/lib/ghc-5.02.2/HSstd.o: unknown symbol `stg_gc_l1'
ghc-5.02.2: panic! (the `impossible' happened, GHC version 5.02.2):
can't load package `std'
[...]
There's
Yes, Sigbjorn is of course right. Disregard my msg ...
J
| Did you bootstrap using itself?
|
| no, that is the pb. Sigbjorn Finne gave the explaination:
|
| GHCi doesn't load the RTS package (nor GMP),
| as they're both baked into the binary. My guess is that
| you've built ghci
I realize that my use of the API was incredibly naïve and
that I should
have been using h* methods with the handle returned from
connectTo. But
it is connectTo that is failing as described.
It fails interactively too with ghci, and regardless of using Server
http or PortNumber 80.
Julian Seward (Intl Vendor) wrote:
| ghc.exe: panic! (the `impossible' happened, GHC version 5.02.1):
| Oversize heap check detected. Please try compiling with -O.
| [...]
Upgrade to 5.02.2, wherein this oversized-heap-check entertainment
is fixed.
Many thanks, Julian! I
I wrote:
I have now upgraded to 5.02.2, which gives me an entirely different
show-stopper bug when using -prof -auto-all:
---begin compilation output
[...output of succesfully compiling a bunch of library modules]
ghc -c -package lang -package concurrent
I don't believe there's a bug in here, only perhaps in
the way the Socket functions are used:
main = withSocketsDo $ do
d - connectTo host port -- (1)
sendTo host port GET / HTTP/1.0\r\n\r\n; -- (2)
response - recvFrom host port; -- (3)
putStrLn response
where
host =
