#4097: Runtime segfaults on +RTS -hr
-------------------------------+--------------------------------------------
    Reporter:  mightybyte      |        Owner:               
        Type:  bug             |       Status:  new          
    Priority:  normal          |    Milestone:               
   Component:  Runtime System  |      Version:  6.12.1       
    Keywords:                  |   Difficulty:               
          Os:  Linux           |     Testcase:               
Architecture:  x86_64 (amd64)  |      Failure:  Runtime crash
-------------------------------+--------------------------------------------
Description changed by igloo:

Old description:

> I get a segfault whenever running the Snap Framework hello world app with
> -hr.  The problem happens with snap-core-0.2.3 and snap-server-0.2.2
> (currently the most recent versions in hackage).  Steps to duplicate:
>
> cabal install snap-server
> mkdir foo && cd foo
> snap init
> cabal configure --enable-executable-profiling
> cabal build
> dist/build/foo/foo +RTS -hr
> httperf --hog --num-conns 1000 --num-calls 1000 --burst-length 20 --port
> 3000 --rate 1000 --uri=/
>
> The problem happens every time I run this httperf command.  Sometimes it
> takes longer than others, but it always crashes for me.  It has also
> happened with previous development versions of Snap, and it also happens
> in the code currently in HEAD as of this writing.
>
> I'm running on a dual quad-core Xeon E5345 with 8 gigs of RAM.

New description:

 I get a segfault whenever running the Snap Framework hello world app with
 -hr.  The problem happens with snap-core-0.2.3 and snap-server-0.2.2
 (currently the most recent versions in hackage).  Steps to duplicate:
 {{{
 cabal install snap-server
 mkdir foo && cd foo
 snap init
 cabal configure --enable-executable-profiling
 cabal build
 dist/build/foo/foo +RTS -hr
 httperf --hog --num-conns 1000 --num-calls 1000 --burst-length 20 --port
 3000 --rate 1000 --uri=/
 }}}
 The problem happens every time I run this httperf command.  Sometimes it
 takes longer than others, but it always crashes for me.  It has also
 happened with previous development versions of Snap, and it also happens
 in the code currently in HEAD as of this writing.

 I'm running on a dual quad-core Xeon E5345 with 8 gigs of RAM.

--

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4097#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to