Summary: | valgrind --leak-check=full memleak errors from system libraries in OS X 10.10.2 | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | jhi |
Component: | memcheck | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mark, rhyskidd |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | MacPorts | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
log from "valgrind --leak-check=full ./zero"
valgrind suppressions file |
Description
jhi
2015-02-25 00:12:05 UTC
Created attachment 91281 [details]
log from "valgrind --leak-check=full ./zero"
Created attachment 91282 [details]
valgrind suppressions file
This appears to be a duplicate of bz#344702. Resolved in r14972. Can you please confirm SVN versions resolve the issue for you? > This appears to be a duplicate of bz#344702. Resolved in r14972. > > Can you please confirm SVN versions resolve the issue for you? I have been using the MacPorts versions of valgrind, I will need to ask the maintainers to pull and build that new version. On Fri, Mar 6, 2015 at 10:22 AM, <rhyskidd@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=344543 > > --- Comment #3 from rhyskidd@gmail.com --- > This appears to be a duplicate of bz#344702. Resolved in r14972. > > Can you please confirm SVN versions resolve the issue for you? > > -- > You are receiving this mail because: > You reported the bug. Ping. Can this be closed as a dup, or is it still alive? On Tuesday-201504-28 6:50, Julian Seward wrote: > https://bugs.kde.org/show_bug.cgi?id=344543 > > --- Comment #5 from Julian Seward <jseward@acm.org> --- > Ping. Can this be closed as a dup, or is it still alive? All I can do is to re-ping the macports people, I will do that right now. AFAICT the macports valgind-devel is based on r14960: sudo port installed | grep valgrind-devel valgrind-devel @3.11.0-r14960_0 (active) so not quite r14972. Confirming this is a dup and has been resolved. jhi will need to follow up the macports team to pull a more current development version: $ cat ../zero.c int main() { return 0; } $ ./vg-in-place ../zero ==90288== Memcheck, a memory error detector ==90288== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==90288== Using Valgrind-3.11.0.SVN and LibVEX; rerun with -h for copyright info ==90288== Command: ../zero ==90288== ==90288== ==90288== HEAP SUMMARY: ==90288== in use at exit: 34,717 bytes in 426 blocks ==90288== total heap usage: 502 allocs, 76 frees, 40,741 bytes allocated ==90288== ==90288== LEAK SUMMARY: ==90288== definitely lost: 0 bytes in 0 blocks ==90288== indirectly lost: 0 bytes in 0 blocks ==90288== possibly lost: 0 bytes in 0 blocks ==90288== still reachable: 0 bytes in 0 blocks ==90288== suppressed: 34,717 bytes in 426 blocks ==90288== ==90288== For counts of detected and suppressed errors, rerun with: -v ==90288== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) $ ./vg-in-place --leak-check=full ../zero ==90291== Memcheck, a memory error detector ==90291== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==90291== Using Valgrind-3.11.0.SVN and LibVEX; rerun with -h for copyright info ==90291== Command: ../zero ==90291== ==90291== ==90291== HEAP SUMMARY: ==90291== in use at exit: 34,717 bytes in 426 blocks ==90291== total heap usage: 502 allocs, 76 frees, 40,741 bytes allocated ==90291== ==90291== LEAK SUMMARY: ==90291== definitely lost: 0 bytes in 0 blocks ==90291== indirectly lost: 0 bytes in 0 blocks ==90291== possibly lost: 0 bytes in 0 blocks ==90291== still reachable: 0 bytes in 0 blocks ==90291== suppressed: 34,717 bytes in 426 blocks ==90291== ==90291== For counts of detected and suppressed errors, rerun with: -v ==90291== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 15 from 15) *** This bug has been marked as a duplicate of bug 344702 *** |