[GHC] #15038: Memory Corruption (strange closure type)

[GHC]

#15038: Memory Corruption (strange closure type)
-------------------------------------+-------------------------------------
        Reporter:  andrewthad        |                Owner:  (none)
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:  8.6.1
       Component:  Compiler          |              Version:  8.4.1
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  Runtime crash     |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by andrewthad):

 Here's my rudimentary analysis of the error message.

 {{{
 internal error: evacuate(static): strange closure type 16648
 }}}

 If this were caused by user code, I think it could only be the result of
 an out-of-bounds call to `writeArray`, `writeByteArray`, `readArray`, or
 `indexArray`. An out of bounds function that reads from a byte array would
 not cause this. It would simply give the user a garbage value. Well, I
 guess if it were far enough out-of-bounds, the operating system would kill
 the process, but that doesn't happen here. The function `writeByteArray`
 is used a few times, but all of its uses look safe to me.

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/15038#comment:6>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler