From mboxrd@z Thu Jan 1 00:00:00 1970 From: walter harms Subject: Re: [PATCH] pldd.1: Document glibc's unbreakage of tool. Date: Mon, 13 May 2019 16:34:07 +0200 Message-ID: <5CD9805F.4040601@bfs.de> References: <20190511072049.2w7pp723iszp3gra@localhost.localdomain> <8736liit24.fsf@oldenburg2.str.redhat.com> Reply-To: wharms@bfs.de Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <8736liit24.fsf@oldenburg2.str.redhat.com> Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org, libc-alpha@sourceware.org List-Id: linux-man@vger.kernel.org Am 13.05.2019 11:48, schrieb Florian Weimer: > * G. Branden Robinson: > >> .SH BUGS >> -Since glibc 2.19, >> +From glibc 2.19 to 2.29, >> .B pldd >> -is broken: it just hangs when executed. >> -.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=18035 >> -It is unclear if it will ever be fixed. >> +was broken: it just hung when executed. >> +.\" glibc commit 1a4c27355e146b6d8cc6487b998462c7fdd1048f >> +This problem was fixed in glibc 2.30. > > I'm not sure if it makes sense to document this in the manual page. I > expect that the fix will propagate to affected distributions fairly > quickly, now that it is available upstream. It's certainly more likely > that users will receive a glibc update with the fix than a manpage > update with this change. > IMHO it should be noted in the BUGS section. You can not rely that you have always the lastest version of libc (at least i do not have) but you may notice a different behavior and it is simply very helpful to have a hint that certain versions are broken. (if someone cares: my problem was with a64l. It suddenly changed behavior ...) just my 2 cents, re, wh