A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1847 
====================================================================== 
Reported By:                philip-guenther
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1847
Category:                   System Interfaces
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Philip Guenther 
Organization:               OpenBSD 
User Reference:              
Section:                    dlfnc.h and dladdr() 
Page Number:                238 and  
Line Number:                8391 and  
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2024-08-02 01:15 UTC
Last Modified:              2024-08-05 14:41 UTC
====================================================================== 
Summary:                    dladdr()'s second argument should be Dl_info*, not
Dl_info_t*
====================================================================== 

---------------------------------------------------------------------- 
 (0006856) geoffclare (manager) - 2024-08-05 14:41
 https://austingroupbugs.net/view.php?id=1847#c6856 
---------------------------------------------------------------------- 
I am in favour of adding Dl_info as a synonym for Dl_info_t.

I am not in favour of deprecating Dl_info_t (with a view to removing it in
Issue 9). Since Solaris 11 has specified Dl_info_t in its dladdr() man page
for many years, there will be existing code which uses it. (And there may
well be more code written between now and TC1 that follows the standard as
published, by people unaware of this request.) I don't see a desire to
"clean this up" as sufficient justification for forcing such code to change
in order for it to conform to Issue 9.

I'd suggest instead that we add some application usage along these lines:
<blockquote>Although this standard requires <b>Dl_info</b> and
<b>Dl_info_t</b> to be defined as synonyms for the same type, historically
many systems only defined <b>Dl_info</b> and did not define
<b>Dl_info_t</b>. Consequently, choosing to use <b>Dl_info</b> over
<b>Dl_info_t</b> may provide better portability to non-conforming
implementations (such as those which conform to earlier versions of this
standard from before <i>dladdr</i>() was added but which also provide
<i>dladdr</i>() as an extension).</blockquote> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-08-02 01:15 philip-guentherNew Issue                                    
2024-08-02 01:15 philip-guentherName                      => Philip Guenther 
2024-08-02 01:15 philip-guentherOrganization              => OpenBSD         
2024-08-02 01:15 philip-guentherSection                   => dlfnc.h and
dladdr()
2024-08-02 01:15 philip-guentherPage Number               => 238 and         
2024-08-02 01:15 philip-guentherLine Number               => 8391 and        
2024-08-05 14:41 geoffclare     Note Added: 0006856                          
======================================================================


  • [1003.1(20... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group

Reply via email to