Comment 6 for bug 235955

Any program compiled with gdc seem to have memory leaks.

$ echo "void main(){}" > test.d ; gdc test.d
$ valgrind ./a.out
==24118== Memcheck, a memory error detector.
==24118== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==24118== Using LibVEX rev 1804, a library for dynamic binary translation.
==24118== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==24118== Using valgrind-3.3.0-Debian, a dynamic binary instrumentation framework.
==24118== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==24118== For more details, rerun with: -v
==24118==
==24118==
==24118== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1)
==24118== malloc/free: in use at exit: 8,248 bytes in 3 blocks.
==24118== malloc/free: 13 allocs, 10 frees, 41,652 bytes allocated.
==24118== For counts of detected errors, rerun with: -v
==24118== searching for pointers to 3 not-freed blocks.
==24118== checked 117,644 bytes.
==24118==
==24118== LEAK SUMMARY:
==24118== definitely lost: 8,200 bytes in 1 blocks.
==24118== possibly lost: 0 bytes in 0 blocks.
==24118== still reachable: 48 bytes in 2 blocks.
==24118== suppressed: 0 bytes in 0 blocks.
==24118== Rerun with --leak-check=full to see details of leaked memory.

I get the same results with gdc-4.1.