[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Memory leak happening while using open ldap with free-radius and samba
- To: Adarsha S <s.adarsha@gmail.com>
- Subject: Re: Memory leak happening while using open ldap with free-radius and samba
- From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
- Date: Fri, 05 Jun 2015 13:39:27 +0200
- Cc: openldap-technical@openldap.org
- In-reply-to: <CA+kZdmhWcFsB=akxTa+BPcX1ZBJcr6P6Jce1U56Y2J8b_hrj-A@mail.gmail.com>
- References: <CA+kZdmgM14E6+Pxa=qT6Q4vbimYaoQ+tp61VLKx57xizo0xEDg@mail.gmail.com> <557184E0.9080202@usit.uio.no> <CA+kZdmhWcFsB=akxTa+BPcX1ZBJcr6P6Jce1U56Y2J8b_hrj-A@mail.gmail.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
On 05. juni 2015 13:27, Adarsha S wrote:
hi Hallvard,
I tried runnig valgrind.But summery showed me possible leak count.
I was not able to co-relate the output with the actual code.
valgrind --help
--show-reachable=no|yes show reachable blocks in leak check? [no]
--show-possibly-lost=no|yes show possibly lost blocks in leak check? [yes]
"possibly lost" = pointer into the memory block instead of to the beginning,
I think. "reachable" = there's a reference to the memory when the program
died, so technically it's not a "leak".
--
Hallvard