tree 5f01024c178f8c529ce91e3bb1fc048457633703
parent fff77e213afe7ecb10914b22fb411aa67ccae834
author Arya K Padman <aryakpadman@gmail.com> 1714364625 -0500
committer Arya K Padman <aryakpadman@gmail.com> 1714630737 +0000

peltool: Fixing memory leak in peltool

On analysis of a defect which points BMC reboot issue, it is found that
peltool has a memory leak which increases the memory consumption on
runtime.

Done the analysis for the same by generating valgrind report for peltool
and figured out that a block of memory which is getting allocated
dynamically in the API dumpHex() is not getting freed properly, results
in memory leak.

Fixing the same by changing the pointer which points to the block of
memory to a unique_ptr.

Tested:
The new valgrind report generated for peltool after adding the changes
shows zero leakage.
```
==883== LEAK SUMMARY:
==883==    definitely lost: 0 bytes in 0 blocks
==883==    indirectly lost: 0 bytes in 0 blocks
==883==      possibly lost: 0 bytes in 0 blocks
==883==    still reachable: 9,786 bytes in 31 blocks
==883==         suppressed: 0 bytes in 0 blocks
```

Signed-off-by: Arya K Padman <aryakpadman@gmail.com>
Change-Id: I55db4feedff3a139d0f44a5ace1778acc7375596