public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "srk31 at srcf dot ucam.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/16262] Semantics of dladdr don't quite match documentation
Date: Tue, 06 May 2014 18:11:00 -0000	[thread overview]
Message-ID: <bug-16262-131-NCcPkFEkzp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16262-131@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Stephen Kell <srk31 at srcf dot ucam.org> ---
Thanks very much to Michael Kerrisk for noticing and fixing this (before I even
got around to reporting it to man-pages :-).

I've also produced a (lightly tested) patch to glibc which optionally enables
the alternative behaviour. It is requested using the flags argument to
dladdr1(). 

I realise there mightn't be much enthusiasm for the use cases of this patch --
my symbol-iteration case, or for porting glibc to non-ELF platforms (where this
behaviour is the only one that's portable). But I thought I'd post it anyway.
The patch attached applies to git as of commit
d359bcc2adc063bae511b1a42a01a301b53c4d39 (15th Jan 2014).

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


  parent reply	other threads:[~2014-05-06 18:11 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
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 [this message]
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-NCcPkFEkzp@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: link
Be 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).