Opened 4 years ago

Closed 4 years ago

#10282 closed bug (duplicate)

Segfault when calling show on an Integer of a certain size

Reported by: gelisam Owned by:
Priority: normal Milestone:
Component: GHCi Version: 7.10.1
Keywords: integer-gmp Cc: hvr
Operating System: MacOS X Architecture: Unknown/Multiple
Type of failure: GHCi crash Test Case:
Blocked By: Blocking:
Related Tickets: 7655 Differential Rev(s):
Wiki Page:


You're not going to believe this.

$ ghc -e 'let k = show (10^184000) in k == k'
$ ghc -e 'let k = show (10^187000) in k == k'
$ ghc -e 'let k = show (10^186000) in k == k'
Bus error

That's right: there is a problem which affects Integer values which are 186000 digits long, but which does not affect values which are 187000 digits long.

So 10^184000 works fine, 10^187000 works fine, but 10^186000 doesn't. What about 10^185000? Well, it depends on your version of GHC. And on chance. GHC is always happy with 10^185000, but GHC 7.8.3 crashes about two-thirds of the time:

$ ghc -e 'let k = show (10^185000) in k == k'
Segmentation fault

And it's a different kind of crash, too! A segmentation fault instead of a "bus error".

I have tried all the lengths in [1000,2000,..,100000], and some lengths are fine, some lengths have a bus error, and some lengths segfault. The most helpful lengths I've encountered give an error message about malloc:

$ ghc -e 'let k = show (10^264000) in k == k'
ghc(72417,0x107081000) malloc: *** error for object 0x107300000: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap

Sometimes it gives a slightly different error message:

$ ghc -e 'let k = show (10^264000) in k == k'
ghc(72453,0x107381000) malloc: *** error for object 0x107200128: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
Abort trap

Anyway, a lot more people posted their results in the following reddit thread, without realizing that the problem had to do with the length:

So far, only folks on OS X have managed to reproduce the problem. The problem occurs with ghci, runhaskell and ghc -e, but not with compiled binaries.

Change History (3)

comment:1 Changed 4 years ago by hvr

Keywords: integer-gmp added

I'm afraid this may require tracing C library calls on OSX in order to find out how this can even go wrong. I'm particularly surprised this happens on both 7.10 and 7.8 which have a rather completely different integer-gmp implementation.

comment:2 Changed 4 years ago by hsyl20

It seems to be a duplicate of #7655

comment:3 Changed 4 years ago by gelisam

Resolution: duplicate
Status: newclosed

Indeed, the problem disappeared after I installed the latest version of GMP from Closing as duplicate (should I do that myself?)

Note: See TracTickets for help on using tickets.