Opened 9 years ago

Closed 8 years ago

#4097 closed bug (fixed)

Runtime segfaults on +RTS -hr

Reported by: mightybyte Owned by:
Priority: normal Milestone: 7.0.1
Component: Runtime System Version: 6.12.1
Keywords: Cc:
Operating System: Linux Architecture: x86_64 (amd64)
Type of failure: Runtime crash Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:

Description (last modified by igloo)

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.

Change History (3)

comment:1 Changed 9 years ago by igloo

Description: modified (diff)

comment:2 Changed 9 years ago by igloo

Milestone: 6.14.1

comment:3 Changed 8 years ago by igloo

Resolution: fixed
Status: newclosed

I've just fixed a retainer profiling segfault, and retainer profiling of GHC now works. The patch will be in the second 7.0.1 release candidate:

Tue Oct 19 14:27:27 BST 2010  Ian Lynagh <igloo@earth.li>             
  * Fix a retainer profiling segfault
  The bitmap type wasn't big enough to hold large bitmaps on 64 bit
  platforms. Profiling GHC was segfaulting when retainStack was handling a
  size 33 bitmap.

I'm optimistically assuming this will fix your segfault too; please reopen if not.

Note: See TracTickets for help on using tickets.