public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <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 12:19:24 +0000	[thread overview]
Message-ID: <bug-26022-131-2hJZ8A4c4L@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 #5 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Claudio Daffra from comment #4)
> 
> 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.

I think the problem is that you are not using glibc on macosx. The libc
implementation you are using on macosx seems to have various bugs and/or leaks,
or might not support __libc_freeres to coordinate with valgrind. You might want
to report those issues to apple, assuming they provided the libc you are using
on macOS.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-06-04 12:19 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
2020-06-04 12:19 ` mark at klomp dot org [this message]
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-2hJZ8A4c4L@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: link
Be 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).