#2703: Buffer overflow, occasional segfaults when using handles created by
Network.
-------------------------------+--------------------------------------------
Reporter: sclv | Owner: igloo
Type: merge | Status: new
Priority: high | Milestone: 6.10.1
Component: libraries/network | Version: 6.8.3
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: x86_64 (amd64)
Os: Linux |
-------------------------------+--------------------------------------------
Changes (by simonmar):
* owner: simonmar => igloo
* type: bug => merge
Comment:
I've found and fixed the cause of the hang, but the segfault eludes me.
I've seen it once (it generated a 6.9GB core file that locked up our NFS
server for quite a while :-) but I've been unable to reproduce it since.
I suspect there's an inaccurate stack check somewhere, but finding those
is particuarly hard. The best we can hope for is that the crash
resurfaces in another way, or (optimistically) that it's already been
fixed.
{{{
Mon Oct 20 05:11:03 PDT 2008 Simon Marlow <[EMAIL PROTECTED]>
* FIX (partially) #2703: bug in stack overflow handling when inside
block
As a result of a previous ticket (#767) we disabled the generation of
StackOverflow exceptions when inside a Control.Exception.block, on the
grounds that StackOverflow is like an asynchronous exception. Instead
we just increase the stack size. However, the stack size calculation
was wrong, and ended up not increasing the size of the stack, with the
result that the runtime just kept re-allocating the stack and filling
up memory.
}}}
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2703#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
