amodra at gmail dot com
2018-05-10 23:01:17 UTC
https://sourceware.org/bugzilla/show_bug.cgi?id=23161
Alan Modra <amodra at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amodra at gmail dot com
--- Comment #1 from Alan Modra <amodra at gmail dot com> ---
I agree that exporting these symbols doesn't seem to be useful. I can't see a
good reason why anyone would want access to their values in shared libraries
external to the given shared library (and to choose a particular _edata say,
from among many possible shared libraries requires dlopen and dlsym).
Also, given that the standard scripts define these symbols for shared
libraries, it isn't simple for a shared library to access their values in the
executable. Again, you'd need to use dlopen and dlsym. So it probably isn't
that useful to export these symbols from an executable, but I'm less sure about
executables than I am about shared libraries.
Alan Modra <amodra at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amodra at gmail dot com
--- Comment #1 from Alan Modra <amodra at gmail dot com> ---
I agree that exporting these symbols doesn't seem to be useful. I can't see a
good reason why anyone would want access to their values in shared libraries
external to the given shared library (and to choose a particular _edata say,
from among many possible shared libraries requires dlopen and dlsym).
Also, given that the standard scripts define these symbols for shared
libraries, it isn't simple for a shared library to access their values in the
executable. Again, you'd need to use dlopen and dlsym. So it probably isn't
that useful to export these symbols from an executable, but I'm less sure about
executables than I am about shared libraries.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are receiving this mail because:
You are on the CC list for the bug.