Re: Valgrind

Yes. It was a relatively recent daily snapshot. But I wouldn't take
anything I gleaned from the run as informative, since I clearly don't
know what I'm doing. ;-)

Florin Andrei wrote:
> Have you tried it with 2.5PRE ?
>
> On Mon, 2002-07-29 at 11:46, Joe Cooper wrote:
>
>>I experimented with Valgrind on Squid yesterday, and couldn't make much
>>sense of the results (still reading the docs). Looked like all
>>complaints were about system libraries rather than Squid itself...But
>>then, I don't think I was using it correctly either. ;-)
>>
>>I'll keep prodding at it in my spare time, as it looks like a nifty tool
>>that I'd be better off knowing how to use.
>>
>>Florin Andrei wrote:
>>
>>>http://developer.kde.org/~sewardj/
>>>
>>>Valgrind is a GPL'd tool to help you find memory-management problems in
>>>your programs. When a program is run under Valgrind's supervision, all
>>>reads and writes of memory are checked, and calls to
>>>malloc/new/free/delete are intercepted. As a result, Valgrind can detect
>>>problems such as:
>>>
>>> * Use of uninitialised memory
>>> * Reading/writing memory after it has been free'd
>>> * Reading/writing off the end of malloc'd blocks
>>> * Reading/writing inappropriate areas on the stack
>>> * Memory leaks -- where pointers to malloc'd blocks are lost forever
>>> * Passing of uninitialised and/or unaddressible memory to system
>>>calls
>>> * Mismatched use of malloc/new/new [] vs free/delete/delete []
>>> * Some misuses of the POSIX pthreads API
>>>
>>
>>
>>
>>--
>>Joe Cooper <joe@swelltech.com>
>>Web caching appliances and support.
>>http://www.swelltech.com
>>
>

-- 
Joe Cooper <joe@swelltech.com>
Web caching appliances and support.
http://www.swelltech.com