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-15 15:33 UTC
====================================================================== 
Summary:                    dladdr()'s second argument should be Dl_info*, not
Dl_info_t*
====================================================================== 

---------------------------------------------------------------------- 
 (0006863) geoffclare (manager) - 2024-08-15 15:33
 https://austingroupbugs.net/view.php?id=1847#c6863 
---------------------------------------------------------------------- 
Interpretation response
------------------------
The standard states that <dlfcn.h> defines Dl_info_t and does not define
Dl_info, and conforming implementations must conform to this. However,
concerns have been raised about this which are being referred to the
sponsor.

Rationale:
-------------
There is existing application code that uses Dl_info_t and existing code
that uses Dl_info. To enable both to be ported to a standard-conforming
environment with minimal change, the standard should define both types.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
After page 238 line 8393 section <dlfcn.h>, add:
<blockquote>The <b><dlfcn.h></b> header shall define the <b>Dl_info</b>
type to be the same type as <b>Dl_info_t</b>.</blockquote>

On page 238 line 8409 section <dlfcn.h>, change APPLICATION USAGE from
"None" to:
<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                          
2024-08-11 01:46 philip-guentherNote Added: 0006859                          
2024-08-11 01:47 philip-guentherNote Added: 0006860                          
2024-08-15 15:33 geoffclare     Note Added: 0006863                          
======================================================================


  • [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