Possible leaks observed in GCC.
Jonathan Wakely
jwakely.gcc@gmail.com
Wed Dec 9 12:53:39 GMT 2020
On Wed, 9 Dec 2020 at 12:45, Tomar, Sourabh Singh via Gcc
<gcc@gcc.gnu.org> wrote:
>
> Hi Folks,
>
> I observed some leaks using valgrind while compiling a sample program using GCC.
This seems more appropriate for gcc-help@gcc.gnu.org instead.
> Could anyone aware of these details provide any insights to these leaks ?
You've provided no information that can tell us anything for sure, but
these are probably leaks caused by your code. You can use valgrind to
find them.
Valgrind tells you what to do:
> ==32090== Rerun with --leak-check=full to see details of leaked memory
More information about the Gcc
mailing list