Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 23 Nov 2020 12:24:28 +0000
From: Jonathan Wakely <>
To: Арсений <>
Cc: Rich Felker <>,,
	Florian Weimer <>
Subject: Re: Mutexes are not unlocking

On 22/11/20 23:05 +0300, Арсений wrote:
>I fixed the problem by making a workaround. Specifying -D_GLIBCXX_GTHREAD_USE_WEAK=0 forces libstdc++ headers do not use weak symbols. Mutexes are correctly locked and unlocked now.

That might "work" but is unsupported, because that macro is for
libstdc++'s internal use, not for users to define/undefine.

But then libstdc++ doesn't support being compiled/linked against a
glibc libstdc++ and then running against musl at runtime (I didn't
even know that was an option until today) so one more unsupported
thing probably won't hurt :-)

Maybe we should just bless the use of that macro as supported, which
would solve

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.