[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: more about proc
From: |
Marcus Brinkmann |
Subject: |
Re: more about proc |
Date: |
Wed, 15 Aug 2001 07:18:53 +0200 |
User-agent: |
Mutt/1.3.20i |
On Wed, Aug 15, 2001 at 12:32:20AM -0400, Roland McGrath wrote:
> It's a good bet the bug is in libihash/ihash.c, since that creates a large
> array of chars on the stack and sets them all to 1 or 0.
This would be libihash/primes.c, it's the sieve used for finding the next
prime number. That's the only char array I could find, and it meets our
requirements (every second entry is ignored, so it is not set to 1. It
seems we can save some stack usage here to generate even higher primes.)
In fact, I am quite confident we could show that the other zeros represent
prime numbers.
A quick review of _ihash_nextprime() did not reveal anything obvious,
but a breakpoint on it and some patience will help. Or someone else finds
the bug?
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann GNU http://www.gnu.org marcus@gnu.org
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de
Re: more about proc, Igor Khavkine, 2001/08/15