Re: Mersenne: Linux mprime and glibc 2.1

1999-08-16 Thread Tom Goulet

 Have you tried to run sprime? (is mprime but linked with static
 libraries). I've got some problems in an old machine with an old linux
 and sprime ran well. In my machine, sprime runs a bit fast than mprime!.

Actually, yes.  sprime and mprime and mprime-specific-for-redhat-6.0 all
act identically.  I blame something to do with ld, my install is rather
ragged. Take a look at this:

[tomg@nova ~/gimps]$ file mprime
mprime: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked (uses 
shared libs), not stripped
[tomg@nova ~/gimps]$ ldd mprime
not a dynamic executable

I get the same file and mprime results for mprime, sprime and mprime-rh6
(except file properly determines that sprime is statically linked).  I doubt
this is a mersenne problem, just something to do with the way my ld is
misbehaving.

TomG
_
Unsubscribe  list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers



Re: Mersenne: Linux mprime and glibc 2.1

1999-08-16 Thread Henrik Olsen

On Mon, 16 Aug 1999, Tom Goulet wrote:
  Have you tried to run sprime? (is mprime but linked with static
  libraries). I've got some problems in an old machine with an old linux
  and sprime ran well. In my machine, sprime runs a bit fast than mprime!.
 
 Actually, yes.  sprime and mprime and mprime-specific-for-redhat-6.0 all
 act identically.  I blame something to do with ld, my install is rather
From my memory of the start of this thread, the behaviour is immediate
segfaults, is this right?

I've seen this on a machine with 16MB ram and no swap.
After checking the code I think I found the reason.  [ms]prime
preallocates 16MB memory, even if it doesn't use it all.  This will cause
the program to fail badly if the memory's not available.
The cure was to add enough swap to appease the initial allocation, which
is then never used, so the swap space isn't really used.
I think I used 10MB swap:)

The machine was one I put together after I did a quick inventory of all
the bits and pieces I had left from all my updates of my primary machine,
and found that the only thing actually missing for it to be a complere
computer was the screen:)

 ragged. Take a look at this:
 
 [tomg@nova ~/gimps]$ file mprime
 mprime: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked (uses 
shared libs), not stripped
 [tomg@nova ~/gimps]$ ldd mprime
 not a dynamic executable
 
 I get the same file and mprime results for mprime, sprime and mprime-rh6
 (except file properly determines that sprime is statically linked).  I doubt
 this is a mersenne problem, just something to do with the way my ld is
 misbehaving.
 
 TomG
 _
 Unsubscribe  list info -- http://www.scruz.net/~luke/signup.htm
 Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers
 

-- 
Henrik Olsen,  Dawn Solutions I/S   URL=http://www.iaeste.dk/~henrik/
Orson Welles: Rosebud. (dies)
Reporter: What does it mean?
Everybody Else: We don't know.
 Citizen Kane, the Movie-A-Minute version


_
Unsubscribe  list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers



Re: Mersenne: Linux mprime and glibc 2.1

1999-08-16 Thread Tom Goulet

 preallocates 16MB memory, even if it doesn't use it all.  This will cause
 the program to fail badly if the memory's not available.
 The cure was to add enough swap to appease the initial allocation, which
 is then never used, so the swap space isn't really used.
 I think I used 10MB swap:)
Bleah.  That's probably it.  Who wants to send me a free harddrive?  :)

TomG
who won't be running mprime until he upgrades his harddiskdrive(s)

_
Unsubscribe  list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers



Re: Mersenne: Linux mprime and glibc 2.1

1999-08-16 Thread Vincent J. Mooney Jr.

Get the Western Digital 18.5 Gig hard drives at 7200 RPM for under $ 300
each.  My system has two.  Now I have to fill 30 + Gig of hard drive space.

At 07:15 PM 8/16/99 -0400, you wrote:
 preallocates 16MB memory, even if it doesn't use it all.  This will cause
 the program to fail badly if the memory's not available.
 The cure was to add enough swap to appease the initial allocation, which
 is then never used, so the swap space isn't really used.
 I think I used 10MB swap:)
Bleah.  That's probably it.  Who wants to send me a free harddrive?  :)

TomG
who won't be running mprime until he upgrades his harddiskdrive(s)

_
Unsubscribe  list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers


_
Unsubscribe  list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers



Re: Mersenne: Linux mprime and glibc 2.1

1999-08-15 Thread Guillermo Ballester Valor

Hi:

"Ethan M. O'Connor" wrote:
 
 (In response to all the mprime segfaulting under glibc 2.1 messages)
 I had some problems a while back with this issue as well, and then
 it suddenly went away. I'm using the potato release of Debian, and
 right now they are tracking the prereleases of glibc 2.1.2 pretty
 closely. I think that the problems started happening with the change
 from glibc 2.1.1 to an early pre-2.1.2, and went away with another
 upgrade.
 

Have you tried to run sprime? (is mprime but linked with static
libraries). I've got some problems in an old machine with an old linux
and sprime ran well. In my machine, sprime runs a bit fast than mprime!.


| Guillermo Ballester Valor   |  
| [EMAIL PROTECTED]  |  
| c/ cordoba, 19  |
| 18151-Ogijares (Spain)  |
| (Linux registered user 1171811) |
_
Unsubscribe  list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ  -- http://www.tasam.com/~lrwiman/FAQ-mers