This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug manual/16262] Semantics of dladdr don't quite match documentation


http://sourceware.org/bugzilla/show_bug.cgi?id=16262

--- Comment #3 from Ondrej Bilka <neleai at seznam dot cz> ---
On Mon, Dec 09, 2013 at 04:32:52PM +0000, srk31 at srcf dot ucam.org wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=16262
> 
> --- Comment #2 from Stephen Kell <srk31 at srcf dot ucam.org> ---
> Thanks for this.
> 
> The man page is a fraction better, but still problematic because it doesn't say
> what it means for an address to be "matching", and this still differs quite a
> bit between ELF and non-ELF cases.
> 
> I've just discovered that the dlsym(3) man page is maintained in the Linux
> man-pages project, so I will contribute a patch there.
> 
> I would also be interested in contributing a patch to glibc which adds a flag
> to dladdr1() for requesting the behaviour I was hoping for, if you think it has
> a chance of being applied.
>
Adding flag is not very likely, it would be simpler to directly write a
function
that iterates symbols for given object.

> I am familiar with dl_iterate_phdr, but it doesn't do what I want. It iterates
> over program headers, whereas I want to iterate over (defined, dynamic)
> symbols.
> 
I meant if its feasible to iterate over headers, for each get size and
call dlsym on each of its bytes backwards.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]