"Chemolli Francesco (USI)" wrote:
> This would show that the leaked memory is not from mempool-related
> allocs, but xallocs or mallocs or whatnot.
Which if true makes them trivial to find with any decent malloc
debugger/tracer. Not more than about 10 minutes job if you have an
environment where the leak can be triggered.
> The fact that you show no leaks leads me to think it might be
> NTLM-auth-related (ouch!), Robert has audited the code found
> nothing though.
My thought also.
You also needs to trace the code. A manual audit usually misses some
small things... at least this is my own experience in the last years of
Squid coding.
> I'm willing to do some debugging and profiling, if anybody could
> help me in this I'd be obviously very happy.
If you run on Linux, then the RedHat "memprof" tool is one very simple
and powerful tool in finding malloc() leaks.
Usage:
Start memprof
Press the "Run" button
Enter the command line for starting Squid with required options. Don't
forget -N
Let it run until you think it has leaked
Push the "Leaks" button.
Tracking down accounted/referenced leaks with this tool is slightly more
difficult. A am thinking about adding a "diff" function to the profile
part of the tool to make this easier.
Regards
Henrik
Received on Wed Oct 03 2001 - 02:40:54 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:23 MST