public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/16262] Semantics of dladdr don't quite match documentation Date: Mon, 09 Dec 2013 16:47:00 -0000 [thread overview] Message-ID: <bug-16262-131-DkX19dhFh6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16262-131@http.sourceware.org/bugzilla/> 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.
next prev parent reply other threads:[~2013-12-09 16:47 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-27 12:10 [Bug dynamic-link/16262] New: " srk31 at srcf dot ucam.org 2013-12-05 23:17 ` [Bug manual/16262] " neleai at seznam dot cz 2013-12-09 16:32 ` srk31 at srcf dot ucam.org 2013-12-09 16:47 ` neleai at seznam dot cz [this message] 2014-01-08 1:08 ` mtk.manpages at gmail dot com 2014-01-08 1:26 ` Ondřej Bílka 2014-01-08 1:26 ` neleai at seznam dot cz 2014-05-06 18:09 ` srk31 at srcf dot ucam.org 2014-05-06 18:11 ` srk31 at srcf dot ucam.org 2014-06-13 11:51 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16262-131-DkX19dhFh6@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).