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: Thu, 05 Dec 2013 23:17:00 -0000 [thread overview] Message-ID: <bug-16262-131-EyFuELgQ2M@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16262-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16262 Ondrej Bilka <neleai at seznam dot cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtk.manpages at gmail dot com, | |neleai at seznam dot cz, | |roland at gnu dot org Component|dynamic-link |manual --- Comment #1 from Ondrej Bilka <neleai at seznam dot cz> --- That is a documentation bug, manpage is bit clearer by saying that If no symbol matching addr could be found, then dli_sname and dli_saddr are set to NULL. Could you provide patch with clarification? Also did you try to use dl_iterate_phdr? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-12-05 23:17 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 ` neleai at seznam dot cz [this message] 2013-12-09 16:32 ` [Bug manual/16262] " srk31 at srcf dot ucam.org 2013-12-09 16:47 ` neleai at seznam dot cz 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-EyFuELgQ2M@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).