That particular memory is freed in reading_get_done_handler().  I test
with a memory checker in place that detects leaks, but that doesn't mean
something hasn't been missed.

If you shut everything down, you can see if OpenIPMI has allocated any
memory it has not freed.  Look at cmdlang/ipmish.c to see how it does
the memory debugging.  Getting everything freed up can be a little
challenging, but not impossible.

Another option is to run under valgrind, mpatrol, or another memory
debugger.  Make sure to *not* run with the OpenIPMI memory debugger then.

-Corey

Noor wrote:

>Hi ,
>
>When i use below library call of OpenIPMI (1.4.19 or even 1.4.21) from
>an application (linux 2.4.22), i notice a memory leak. The call is
>made in an application loop. Mem leak tools
>point to  the allocs in stand_ipmi_sensor_get_reading etc and the
>absense of corresponding free.
>
>The library call i make for my callback handler is:
>ipmi_sensor_id_get_reading(ipmi_sensor_id_t       sensor_id,
>                           ipmi_sensor_reading_cb done,
>                           void                   *cb_data)
>
>In the libray this function, after some levels of nesting, calls:
>stand_ipmi_sensor_get_reading() where info ptr is malloc'd.
>In error cases ipmi_mem_free(info) is called  immediately in these chain of
>function calls.
>In success cases it seems to be called when the operation
>is done via: reading_get_done_handler.
>
>Eg:
>reading_get
> `-sensor_done_check_rsp
>    `- reading_get_done_handler <-- ipmi_free_mem() here
>
>However in cases like below, i dont see the done handler (free).
>    reading_get_start
>     `-sensor_done_check_rsp
>
>Could this be a source of leak.
>Any pointer on how to debug further, especially to check if the
>asynchronous de-queued operations are completed and info ptr is freed?
>
>do  we need to throttle the rate of above get_reading handler
>operation from application?
>
>Thanks
>Noor
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
>_______________________________________________
>Openipmi-developer mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/openipmi-developer
>  
>



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer

Reply via email to