SIGSEGV in yieldCapability ()

newer
GHC 7, Platform 2011.2 vs OS X...

Johannes Waldmann

22 May 2011 22 May '11

8:31 a.m.

Hi. What would be the reason for Program received signal SIGSEGV, Segmentation fault. 0x00000000006071de in yieldCapability () (gdb) where #0 0x00000000006071de in yieldCapability () #1 0x000000000060bc6b in schedule () #2 0x0000000000609294 in real_main () #3 0x000000000060938d in hs_main () #4 0x00007ffff6b07eff in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x000000000040a589 in _start () this happens in a program compiled with ghc-7.0.3 (and also, with ghc-6.12.3), running with +RTS -N on i7-920, ubuntu 11 (kernel 2.6.38-8) Could this simply mean "heap exhausted"? Thanks - J.W.

Show replies by date

Felipe Almeida Lessa

22 May 22 May

8:47 a.m.

New subject: SIGSEGV in yieldCapability ()

On Sun, May 22, 2011 at 9:31 AM, Johannes Waldmann wrote:

...

Hi. What would be the reason for

Program received signal SIGSEGV, Segmentation fault.

Looks like a bad bug, we shouldn't expect segmentation faults on the runtime system. I think you should file a bug report with a test case on GHC. Cheers =), -- Felipe.

Johannes Waldmann

9:03 a.m.

New subject: SIGSEGV in yieldCapability ()

...

I think you should file a bug report with a test case on GHC.

I am willing to work on this, but I thought I'd go fishing for some advice first. My program uses: forkIO, STM, and FFI. I think that "heap exhausted" sometimes gets reported as "evacuate: strange closure", (cf. http://hackage.haskell.org/trac/ghc/ticket/5085 ) and yieldCapability() might be another instance. Thanks - J.W.

Erik Hesselink

23 May 23 May

4:55 a.m.

New subject: SIGSEGV in yieldCapability ()

On Sun, May 22, 2011 at 15:03, Johannes Waldmann wrote:

...

...
I think you should file a bug report with a test case on GHC.

I am willing to work on this, but I thought I'd go fishing for some advice first. My program uses: forkIO, STM, and FFI.

I've seen something like this, using only forkIO, so I'd start looking there. I was trying to create a reduced test case, but haven't reported a bug yet.

...

I think that "heap exhausted" sometimes gets reported as "evacuate: strange closure", (cf. http://hackage.haskell.org/trac/ghc/ticket/5085 ) and yieldCapability() might be another instance.

Thank you, we just had this message, and I had no idea what it was. Erik

Simon Marlow

24 May 24 May

7:53 a.m.

New subject: SIGSEGV in yieldCapability ()

On 23/05/2011 09:55, Erik Hesselink wrote:

...

On Sun, May 22, 2011 at 15:03, Johannes Waldmann wrote:

...
...
I think you should file a bug report with a test case on GHC.

I am willing to work on this, but I thought I'd go fishing for some advice first. My program uses: forkIO, STM, and FFI.

I've seen something like this, using only forkIO, so I'd start looking there. I was trying to create a reduced test case, but haven't reported a bug yet.

...
I think that "heap exhausted" sometimes gets reported as "evacuate: strange closure", (cf. http://hackage.haskell.org/trac/ghc/ticket/5085 ) and yieldCapability() might be another instance.

Thank you, we just had this message, and I had no idea what it was.

Please report all crashes like this as bugs: http://hackage.haskell.org/trac/ghc/wiki/ReportABug In particular, the RTS should never trigger a crash in a heap exhausted situation - if some documentation somewhere gives the wrong impression about that, please let me know. I will need a reproducible test case to track down the bug, though. Cheers, Simon

5111

Age (days ago)

5113

Last active (days ago)

List overview

Download

4 comments

4 participants

participants (4)

Erik Hesselink
Felipe Almeida Lessa
Johannes Waldmann
Simon Marlow