httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitesh Naik" <nit...@zedo.com>
Subject Re: how to avoid overrun in apache
Date Fri, 11 Mar 2005 14:19:09 GMT
The problem is when apache  reinitializes modules for the second time to
make sure that it will come up after graceful.

Don't know what this process is called.

----- Original Message ----- 
From: "Andy Armstrong" <andya@apache.org>
To: <dev@httpd.apache.org>
Sent: Friday, March 11, 2005 7:21 PM
Subject: Re: how to avoid overrun in apache


> 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
>


Mime
View raw message