#3539: internal error: ASSERTION FAILED: file sm/Evac.c, line 368
-------------------------------+--------------------------------------------
    Reporter:  elaforge        |        Owner:  simonmar
        Type:  bug             |       Status:  new     
    Priority:  high            |    Milestone:  6.12.1  
   Component:  Runtime System  |      Version:  6.10.4  
    Severity:  normal          |   Resolution:          
    Keywords:                  |   Difficulty:  Unknown 
    Testcase:                  |           Os:  MacOS X 
Architecture:  x86             |  
-------------------------------+--------------------------------------------
Comment (by elaforge):

 I'm just noting that this is still happening, with some regularity.  I
 haven't updated because I don't have much more info yet.  I tried
 disabling parallel GC with -g1 but it still happens.

 It usually happens at startup, but has happened while running as well.

 Further logging shows that on startup it's happening either in between
 marshal and a foreign call, or right after the foreign call (but before
 the foreign call starts running).  I'm suspicious of marshaling code
 because it's an opportunity to stomp on memory, but of the pokes called,
 one is withCString and the two custom ones are simply lines of "(#poke
 Struct, attr) structp val" so nothing is obviously wrong there.  My guess
 is something is stomping on memory in a way that the GC is tripping over
 it, so the stomper could have been a while in the past.

 There's a reasonable chance this is simply my own code since I do have to
 marshal structs for C, but this didn't show up on 6.10, so if it's not a
 ghc problem then it's something ghc does differently now that didn't used
 to trip over it.

 Clues on how to track this beyond putting in prints would be much
 appreciated!  Since it's a GC thing, and occurs unpredictably, prints in
 my code probably won't help much anyway.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3539#comment:5>
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