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

GHC ghc-devs at haskell.org
Wed Apr 25 06:52:34 UTC 2018


#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 osa1):

 Thanks for simplifying the code.

 I made an attempt at removing unboxed sums (and had to remove some unboxed
 tuples on the way) [https://github.com/andrewthad/corrupted-memory-
 example/pull/1 here], and that made the bug disappear. So this may be
 related with unboxed tuples/sums.

 > If I use my parser language to simply build up a parser, and then I run
 the parser

 Can you elaborate on this? What do you mean by building your parser
 language? Can you share the code?

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


More information about the ghc-tickets mailing list