mailing list of musl libc
 help / color / mirror / code / Atom feed
From: pierre <pierre@silentlife.com>
To: musl@lists.openwall.com
Subject: Re: dladdr()
Date: Mon, 21 Jan 2013 07:58:20 +0100	[thread overview]
Message-ID: <1358751500.2196.20.camel@6-core> (raw)
In-Reply-To: <20130121020335.GO20323@brightrain.aerifal.cx>


> is dladdr otherwise working correctly for you now?

In the simple example I provided, it always works.
I have added loaded modules with conflicting symbols
and dladdr() also works as expected.

But for my main application (which populates backtraces
with dladdr), musl dladdr() works in DEBUG mode and 
crashes in RELEASE mode. I did not have time to isolate
the problem in a reproducible code snippet but I will
let you know when I have done that.

Knowing that dladdr() crashes should help you anyway:
it might be related to searching addresses that are 
out of the specified module scope (stack smashing?), or
to the ability to be resilient to introspecting itself 
(hence the success of the musl DEBUG code, as well as 
of the bulky GLIBC).

I don't use BSD so I can't tell what they _do_.

I appreciate musl and intend to contribute, especially
in the areas where my application is using libc in 
cornersome areas.

I also find the idea of a musl-based Linux distro rather
attractive as it will immensely reduce the surface of
uncertainty.

Pierre



  reply	other threads:[~2013-01-21  6:58 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 17:17 malloc(0) behaviour Igmar Palsenberg
2013-01-14 18:05 ` Rich Felker
2013-01-14 22:22   ` Strake
2013-01-14 23:05     ` Rich Felker
2013-01-15  8:32     ` Igmar Palsenberg
2013-01-15 12:53       ` Rob Landley
2013-01-15 22:18         ` Igmar Palsenberg
2013-01-15  8:31   ` Igmar Palsenberg
2013-01-15 11:06     ` Szabolcs Nagy
2013-01-15 12:33       ` Igmar Palsenberg
2013-01-15 13:48         ` Rich Felker
2013-01-15 22:28           ` Igmar Palsenberg
2013-01-15 23:22             ` Rob
2013-01-16  7:46               ` Igmar Palsenberg
2013-01-15 13:46       ` Rich Felker
2013-01-15 12:52     ` Rob Landley
2013-01-14 23:37 ` Rob Landley
2013-01-15  0:24   ` Rich Felker
2013-01-15 12:17     ` Rob Landley
2013-01-15  9:01   ` Igmar Palsenberg
2013-01-15 12:58     ` Rob Landley
2013-01-15 14:54       ` dladdr() pierre
2013-01-15 18:48         ` dladdr() Rich Felker
2013-01-16 11:00           ` dladdr() pierre
2013-01-16 12:51             ` dladdr() Szabolcs Nagy
2013-01-16 14:24               ` dladdr() musl
2013-01-16 15:20                 ` dladdr() pierre
2013-01-16 16:49                 ` dladdr() Rich Felker
2013-01-16 17:42                   ` dladdr() musl
2013-01-21  2:03                     ` dladdr() Rich Felker
2013-01-21  6:58                       ` pierre [this message]
2013-01-21 18:35                         ` dladdr() Rich Felker
2013-01-22  6:27                           ` dladdr() pierre
2013-01-22 13:07                             ` dladdr() Szabolcs Nagy
2013-01-22 13:40                               ` dladdr() pierre
2013-01-22 13:51                                 ` dladdr() Rich Felker
2013-01-22 14:59                                   ` dladdr() pierre
2013-01-22 16:11                                     ` dladdr() Szabolcs Nagy
2013-01-22 23:43                                       ` dladdr() Rich Felker

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=1358751500.2196.20.camel@6-core \
    --to=pierre@silentlife.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).