topic Re: Shared library memory leak detection in Operating System - HP-UX

Shared library memory leak detection

Muthukumar_5 — Thu, 10 Jun 2004 04:03:55 GMT

Hai all.

I have my own sample shared library with memory leak which contains no debug symbols on IPF platform.
Which of the following method is good to detect the memory leak.
1. gdb with librtc library
2. using purify tool

Thanks,
Muthu

Re: Shared library memory leak detection

Ravi_8 — Thu, 10 Jun 2004 05:36:53 GMT

Hi Muthu

gdb is the better tool, we use it very often to detect the memory leakage

Re: Shared library memory leak detection

Muthukumar_5 — Thu, 10 Jun 2004 05:54:36 GMT

Hai Ravi,

Thanks for the reply.
Is it good to keep track the memory leaks in the shared libraries and filing JAG's with GDB.

Normally memory leaks are filled using the purify tool. So is there any difference to file the jag with these two scenario's?

Thanks,
Muthu.

Re: Shared library memory leak detection

Manish Srivastava — Thu, 10 Jun 2004 06:09:52 GMT

Hi,

We use purify and it really helps us to catch the MLK's and PLK's. It has been used in our work area with great success. Apart from memory leaks purify reports many other things like array bound read/write etc. The logs help us to keep track of introduction of any problem with new code added.

manish