public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daffra.claudio at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/26022] valgrind gives me error when fwprintf in stderr Date: Thu, 04 Jun 2020 09:45:19 +0000 [thread overview] Message-ID: <bug-26022-131-y2rJwRvTP9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26022-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26022 --- Comment #4 from Claudio Daffra <daffra.claudio at gmail dot com> --- file to reproduce valgrind error #include <stdio.h> #include <wchar.h> int main ( void ) { return 0 ; } error message ==1596== Memcheck, a memory error detector ==1596== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1596== Using Valgrind-3.16.0.GIT and LibVEX; rerun with -h for copyright info ==1596== Command: ./prova ==1596== ==1596== ==1596== HEAP SUMMARY: ==1596== in use at exit: 13,697 bytes in 158 blocks ==1596== total heap usage: 172 allocs, 14 frees, 18,441 bytes allocated ==1596== ==1596== LEAK SUMMARY: ==1596== definitely lost: 0 bytes in 0 blocks ==1596== indirectly lost: 0 bytes in 0 blocks ==1596== possibly lost: 4,392 bytes in 5 blocks ==1596== still reachable: 9,305 bytes in 153 blocks ==1596== suppressed: 0 bytes in 0 blocks ==1596== Rerun with --leak-check=full to see details of leaked memory ==1596== ==1596== For lists of detected and suppressed errors, rerun with: -s ==1596== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4) claudio@RastanX Documents % compiler version claudio@RastanX Documents % gcc -v Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1 Apple clang version 11.0.3 (clang-1103.0.32.59) Target: x86_64-apple-darwin19.5.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin s.o : macOS 10.15.5 (19F96) with --leak-check=full valgrind gives me many other errors. this occurs in macosx only,nothing to do with streams. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-04 9:45 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-22 7:45 [Bug libc/26022] New: " daffra.claudio at gmail dot com 2020-05-22 20:07 ` [Bug libc/26022] " carlos at redhat dot com 2020-05-29 19:40 ` mark at klomp dot org 2020-05-29 20:09 ` carlos at redhat dot com 2020-06-04 9:45 ` daffra.claudio at gmail dot com [this message] 2020-06-04 12:19 ` mark at klomp dot org 2020-06-04 16:58 ` daffra.claudio at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-26022-131-y2rJwRvTP9@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).