Your message dated Sat, 16 May 2009 14:02:25 +0200
with message-id <4a0eab51.2070...@debian.org>
and subject line fixed in NMU
has caused the Debian Bug report #528812,
regarding GMP on ppc64: gcc ICE: Segmentation fault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
528812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgmp3c2
Version: 2:4.2.4+dfsg-8
Severity: grave
I have a problem related to #528768 on my PS3 (which is a ppc64 machine),
but which is sufficiently different to warrant a separate report:
For some files (deterministically, but for maybe 10% of my project C files),
GCC crash:
/src/headers -I../src/graph -o plotport.o ../src/graph/plotport.c
../src/graph/plotport.c: In function 'rectticks':
../src/graph/plotport.c:477: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions.
make: *** [plotport.o] Error 1
This is very reproducible and independant whether I install the lib64gmp
packages.
The error occurs inside cc1 which is linked to libgmp3c2.
Here the GDB output:
Program received signal SIGSEGV, Segmentation fault.
0x0ffbd420 in mpfr_tmp_free () from /usr/lib/libmpfr.so.1
(gdb) list
No symbol table is loaded. Use the "file" command.
(gdb) bt
#0 0x0ffbd420 in mpfr_tmp_free () from /usr/lib/libmpfr.so.1
#1 0x0ff98bfc in mpfr_mul () from /usr/lib/libmpfr.so.1
#2 0x0ff902c4 in mpfr_agm () from /usr/lib/libmpfr.so.1
#3 0x0ff97e24 in mpfr_log () from /usr/lib/libmpfr.so.1
#4 0x1007a240 in ?? ()
#5 0x10082b14 in ?? ()
#6 0x1008440c in ?? ()
...
So far I have tested the following combination:
sid GCC + sid GMP -> crash
lenny GCC + backported sid GMP -> crash
lenny GCC + lenny GMP -> OK
lenny GCC + special lib64gmp build from Etch GMP -> OK
etch GCC + special lib64gmp build from Etch GMP -> OK
Cheers,
--
Bill. <ballo...@debian.org>
Imagine a large red swirl here.
--- End Message ---
--- Begin Message ---
Version: 2:4.2.4+dfsg-8.1
--- End Message ---
