From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/2641 Path: news.gmane.org!not-for-mail From: pierre Newsgroups: gmane.linux.lib.musl.general Subject: Re: dladdr() Date: Mon, 21 Jan 2013 07:58:20 +0100 Message-ID: <1358751500.2196.20.camel@6-core> References: <1358206649.32505.21@driftwood> <22145EB4-CF32-4BCA-8DE6-93790F3E267F@palsenberg.com> <1358254713.32505.27@driftwood> <1358261684.3766.10.camel@6-core> <20130115184820.GA20323@brightrain.aerifal.cx> <1358334018.2170.23.camel@6-core> <20130116125119.GA27914@port70.net> <50F6B818.1070807@gmail.com> <20130116164943.GD20323@brightrain.aerifal.cx> <50F6E698.3070604@gmail.com> <20130121020335.GO20323@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1358751501 29234 80.91.229.3 (21 Jan 2013 06:58:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Jan 2013 06:58:21 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-2642-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 21 07:58:40 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1TxBL5-0002Cp-Mp for gllmg-musl@plane.gmane.org; Mon, 21 Jan 2013 07:58:39 +0100 Original-Received: (qmail 3612 invoked by uid 550); 21 Jan 2013 06:58:21 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 3604 invoked from network); 21 Jan 2013 06:58:21 -0000 Original-Reply-To: pierre@silentlife.com In-Reply-To: <20130121020335.GO20323@brightrain.aerifal.cx> X-Mailer: Evolution 3.2.3-0ubuntu6 Xref: news.gmane.org gmane.linux.lib.musl.general:2641 Archived-At: > 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