Description of problem:
memory leak: 25,830 bytes in 315 blocks are definitely lost
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. valgrind --leak-check=full --log-file=valgrind.log ipmitool -I lanplus -H <> -U USERID -P PASSW0RD sol activate
2.# generate some traffic on the serial console on the PowerEdge machine (e.g. cat /var/log/messages; dmesg; while true; do yes; done; ...)
# kill (gently, with sigint or sigterm) the ipmitool
3. check valgrind.log
==14834== LEAK SUMMARY:
==14834== definitely lost: 27,852 bytes in 339 blocks
==14834== indirectly lost: 0 bytes in 0 blocks
==14834== possibly lost: 0 bytes in 0 blocks
==14834== still reachable: 452 bytes in 8 blocks
==14834== suppressed: 0 bytes in 0 blocks
==14834== Reachable blocks (those to which a pointer was found) are not shown.
==14834== To see them, rerun with: --leak-check=full --show-reachable=yes
==14834== For counts of detected and suppressed errors, rerun with: -v
==14834== Use --track-origins=yes to see where uninitialised values come from
==14834== ERROR SUMMARY: 1166606 errors from 124 contexts (suppressed: 37 from 10)
no memory leak
Created attachment 519005 [details]
see the whole valgrind output
Looks like bug #576004, fixed in RHEL 5.6.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.