Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <076901c525fa$f6ee47f0$ad0110ac@nitesh>
References: <062f01c5257d$531bfcd0$ad0110ac@nitesh>
 <cc67648e0503101202d18807b@mail.gmail.com>
 <076901c525fa$f6ee47f0$ad0110ac@nitesh>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2a894f9fa9be365eba1457767717cdeb@apache.org>
Content-Transfer-Encoding: 7bit
From: Andy Armstrong <andya@apache.org>
Subject: Re: how to avoid overrun in apache
Date: Fri, 11 Mar 2005 13:51:43 +0000
To: dev@httpd.apache.org

On 11 Mar 2005, at 05:27, Nitesh Naik wrote:
> ****  Purify instrumented /servers/run/apache/bin/httpd (pid 8850)  
> ****
> UMR: Uninitialized memory read:
>   * This is occurring while in thread 1074225280:
>         SHA1_Update    [libcrypto.a]
>   * Reading 1 byte from 0x8f7293f in the heap.
>   * Address 0x8f7293f is 31 bytes into a malloc'd block at 0x8f72920 
> of 32
> bytes.
>   * This block was allocated from thread 1074225280:
>         malloc         [rtlib.o]
>         default_malloc_ex [libcrypto.a]

That isn't a buffer overrun - it's an attempt to read uninitialised 
memory. While it's not usually good practice it doesn't necessarily 
mean that the code in question is incorrect.

That's unless I'm completely misreading what Purify is saying.

-- 
Andy Armstrong, hexten.net