Skip to content
  • Simon Marlow's avatar
    In the DEBUG rts, track when CAFs are GC'd · e82fa829
    Simon Marlow authored
    This resurrects some old code and makes it work again.  The idea is
    that we want to get an error message if we ever enter a CAF that has
    been GC'd, rather than following its indirection which will likely
    cause a segfault.  Without this patch, these bugs are hard to track
    down in gdb, because the IND_STATIC code overwrites R1 (the pointer to
    the CAF) with its indirectee before jumping into bad memory, so we've
    lost the address of the CAF that got GC'd.
    
    Some associated refactoring while I was here.
    e82fa829