GNU bug report logs - #40793
Documentation suggestion

Previous Next

Package: libtool;

Reported by: Reuben Thomas <rrt <at> sc3d.org>

Date: Thu, 23 Apr 2020 12:16:02 UTC

Severity: normal

Done: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 40793 in the body.
You can then email your comments to 40793 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-libtool <at> gnu.org:
bug#40793; Package libtool. (Thu, 23 Apr 2020 12:16:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Reuben Thomas <rrt <at> sc3d.org>:
New bug report received and forwarded. Copy sent to bug-libtool <at> gnu.org. (Thu, 23 Apr 2020 12:16:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Reuben Thomas <rrt <at> sc3d.org>
To: bug-libtool <at> gnu.org
Subject: Documentation suggestion
Date: Thu, 23 Apr 2020 13:15:30 +0100
[Message part 1 (text/plain, inline)]
libtool.texi contains the following:

"It was reported that GNU/Linux's glibc 2.0's 'dlopen' with 'RTLD_LAZY'
(that libltdl uses by default) is not thread-safe, but this problem is
supposed to be fixed in glibc 2.1.  On the other hand, 'RTLD_NOW' was
reported to introduce problems in multi-threaded applications on FreeBSD."

I suggest removing this material: glibc 2.1 was released over 20 years ago.
I have looked through both the glibc changelogs and git history to try to
ascertain whether in fact this bug was mentioned as being fixed, but I can
find nothing relevant. The same applies to the FreeBSD case.

Evidence on the positive side is that dlopen(3) states explicitly that the
function is thread safe, and POSIX defines it as such. Therefore it might
be reasonable to state that modern dlopen implementations should be threads
safe. Or it might not. (Does someone know more about this?) In the latter
case, the rest of the paragraph could be left as-is, which is to say,
reasonably conservative.

-- 
https://rrt.sc3d.org
[Message part 2 (text/html, inline)]

Reply sent to Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>:
You have taken responsibility. (Fri, 15 Mar 2024 17:50:02 GMT) Full text and rfc822 format available.

Notification sent to Reuben Thomas <rrt <at> sc3d.org>:
bug acknowledged by developer. (Fri, 15 Mar 2024 17:50:02 GMT) Full text and rfc822 format available.

Message #10 received at 40793-done <at> debbugs.gnu.org (full text, mbox):

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 40793-done <at> debbugs.gnu.org
Subject: Re: Documentation suggestion
Date: Fri, 15 Mar 2024 19:48:00 +0200
[Message part 1 (text/plain, inline)]
Thank you for your bug report! I have removed the warnings about
thread safety with 'dlopen' in libtool's documentation.

-- 
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]
[OpenPGP_signature.asc (application/pgp-signature, attachment)]

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 13 Apr 2024 11:24:15 GMT) Full text and rfc822 format available.

This bug report was last modified 10 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.