From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id E004E398545E; Fri, 29 May 2020 19:40:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E004E398545E
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: Fri, 29 May 2020 19:40:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.27
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mark at klomp dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status cc resolution everconfirmed
 cf_reconfirmed_on
Message-ID: <bug-26022-131-J04jdY02YJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26022-131@http.sourceware.org/bugzilla/>
References: <bug-26022-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2020 19:40:28 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D26022

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |mark at klomp dot org
         Resolution|INVALID                     |---
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-05-29

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Carlos O'Donell from comment #1)
> I've filed a Valgrind bug here:
> https://bugs.kde.org/show_bug.cgi?id=3D421931
>=20
> Please feel free to follow up there if you think it needs an update or you
> want to give a +1 regarding your use case.
>=20
> I'm marking this RESOLVED/INVALID for glibc.

As discussed in that bug, lets reconsider if this is something that can be
cleaned up or clarified in glibc. valgrind itself doesn't use streams, or e=
ven
link against glibc itself. When valgrind "calls" __libc_freeres the user
process as already exitted, no other code/threads that could call into glibc
will run during or after the call to __libc_freeres. Are there any other us=
ers
of __libc_freeres that might not make those guarantees?

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