[MLton-user] *** glibc detected *** realloc(): invalid pointer

[Wesley W. Terpstra]

Has anyone else noticed that gmp seems to be broken as of today? My system
hasn't changed, and I downgraded to MLton 20061107 on my completely normal
etch machine. However, when I try to execute MLton-generated executables
now, I often get the error:
*** glibc detected *** realloc(): invalid pointer: 0x6e8ecdc8 ***
which seems to be coming from gmp:
Program received signal SIGABRT, Aborted.
0xffffe405 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe405 in __kernel_vsyscall ()
#1  0x55609811 in raise () from /lib/tls/i686/cmov/libc.so.6
#2  0x5560afb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#3  0x5563edfa in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#4  0x55649063 in realloc () from /lib/tls/i686/cmov/libc.so.6
#5  0x556490b1 in realloc () from /lib/tls/i686/cmov/libc.so.6
#6  0x55648dcc in realloc () from /lib/tls/i686/cmov/libc.so.6
#7  0x55581559 in __gmp_default_reallocate () from /usr/lib/libgmp.so.3
#8  0x55596916 in __gmpz_realloc () from /usr/lib/libgmp.so.3
#9  0x55593965 in __gmpz_mul () from /usr/lib/libgmp.so.3
#10 0x0899c3af in ?? ()
...

What I find particularly worrying is that AFAIK, when MLton calls gmpz_mul,
gmp should NEVER need to realloc the integer..? Is this some sort of Y2008
bug in gmp? Has anyone else started experiencing it as of today? It doesn't
always happen to me, but trying to build MLton seems a sure-fire way to
trigger it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mlton.org/pipermail/mlton-user/attachments/20080819/b5c3c9bd/attachment.htm