tags 470557 + moreinfo stop Hello Török,
Thanks for the detailed bug report and your interest in improving Deiban. I'm just doing some cleanup, I am not a maintainer of the GCC package in Debian. (You will have to CC me if you want me to receive possible replies). The package name of these bug reports is not present in Debian, and the bug is orphan now (without assigned package/maintainer), which it means that, even if not closed, people probably will not pay any attention to it anymore (it will have to be reassigned to a package name in active releases). According to the following URL, the package was removed from official repositories back in 2009: http://packages.qa.debian.org/g/gcc-4.2.html I tried to reproduce the bug myself with current versions of GCC, and the problem seems fixed: $ gcc --version | head -1 gcc (Debian 4.7.2-4) 4.7.2 $ gcc -O3 gcc42_O3_bug.i $ ./a.out $ valgrind ./a.out ==29045== Memcheck, a memory error detector ==29045== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==29045== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==29045== Command: ./a.out ==29045== ==29045== ==29045== HEAP SUMMARY: ==29045== in use at exit: 0 bytes in 0 blocks ==29045== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==29045== ==29045== All heap blocks were freed -- no leaks are possible ==29045== ==29045== For counts of detected and suppressed errors, rerun with: -v ==29045== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4) $ gcc -O3 -finline-functions gcc42_O3_bug.i $ ./a.out $ valgrind ./a.out ==29061== Memcheck, a memory error detector ==29061== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==29061== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==29061== Command: ./a.out ==29061== ==29061== ==29061== HEAP SUMMARY: ==29061== in use at exit: 0 bytes in 0 blocks ==29061== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==29061== ==29061== All heap blocks were freed -- no leaks are possible ==29061== ==29061== For counts of detected and suppressed errors, rerun with: -v ==29061== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4) Can you reproduce the bug, or do you think that the bug might be still present? If so, we should reassign the bug to the current package names. Or otherwise, can we close the bug report? Cheers. -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
