Description of problem:
memory leak: 25,830 bytes in 315 blocks are definitely lost

Version-Release number of selected component (if applicable):
ipmitool-1.8.11-11.el6.i686

How reproducible:
deterministic

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
  
Actual results:
==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== 
==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)


Expected results:
no memory leak

Additional info: