Possible leaks observed in GCC.

[Tomar, Sourabh Singh]

Hi Folks,

I observed some leaks using valgrind while compiling a sample program using GCC.

Could anyone aware of these details provide any insights to these leaks ?

Command line Details:
$ valgrind gcc main.c -g
==32090== Memcheck, a memory error detector
==32090== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==32090== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==32090== Command: gcc main.c -g
==32090==
==32090==
==32090== HEAP SUMMARY:
==32090==     in use at exit: 171,779 bytes in 101 blocks
==32090==   total heap usage: 394 allocs, 293 frees, 222,596 bytes allocated
==32090==
==32090== LEAK SUMMARY:
==32090==    definitely lost: 6,019 bytes in 36 blocks
==32090==    indirectly lost: 82 bytes in 5 blocks
==32090==      possibly lost: 0 bytes in 0 blocks
==32090==    still reachable: 165,678 bytes in 60 blocks
==32090==         suppressed: 0 bytes in 0 blocks
==32090== Rerun with --leak-check=full to see details of leaked memory
==32090==
==32090== For counts of detected and suppressed errors, rerun with: -v
==32090== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Cheers,
Sourabh.