Mersenne: mprime crashes in linux 2.4.8

2002-04-13 Thread Pierre Abbat

I was running mprime 21.4.2 under Linux 2.4.3 for many months with no 
problem. I just rebooted into 2.4.8 (both are stock kernels from Mandrake) 
and mprime segfaulted. I ran gdb on it and got the following:

[root@littlecat mersenne]# gdb
GNU gdb 4.17.0.4 with Linux/x86 hardware watchpoint and FPU support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux".
(gdb) file ./mprime
Reading symbols from ./mprime...(no debugging symbols found)...done.
(gdb) run
Starting program: /win/mersenne/./mprime
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x8172105 in _IO_stdin_used ()
(gdb) where
#0  0x8172105 in _IO_stdin_used ()
#1  0x40015c24 in _dl_debug_mask ()
#2  0x8056136 in strcpy ()
#3  0x80744bc in strcpy ()
#4  0x8073dde in strcpy ()
#5  0x4005e5b0 in __libc_start_main ()
(gdb)
[root@littlecat mersenne]# gdb
GNU gdb 4.17.0.4 with Linux/x86 hardware watchpoint and FPU support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux".
(gdb) file ./mprime
Reading symbols from ./mprime...(no debugging symbols found)...done.
(gdb) run
Starting program: /win/mersenne/./mprime
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x8172105 in _IO_stdin_used ()
(gdb) where
#0  0x8172105 in _IO_stdin_used ()
#1  0x40015c24 in _dl_debug_mask ()
#2  0x8056136 in strcpy ()
#3  0x80744bc in strcpy ()
#4  0x8073dde in strcpy ()
#5  0x4005e5b0 in __libc_start_main ()
(gdb)

ldd returns the following information:

libm.so.6 => /lib/libm.so.6 (0x4001f000)
libc.so.6 => /lib/libc.so.6 (0x40042000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)

What's wrong?
_
Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers



Mersenne: Database merge

2002-04-13 Thread George Woltman

Hello all,

Brad at Entropia has just done a database merge in another attempt
to get rid of the exponents below 4,000,000 that have mysteriously appeared
in the cleared exponents and active assignments reports.  It looks like
we may not have succeeded :(

Just thought you folks might be curious as to why a merge took
place just a week or two after the last one.

-- George

_
Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers