From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14597 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Guillaume Quintard Newsgroups: gmane.linux.lib.musl.general Subject: Re: libexecinfo with musl Date: Mon, 26 Aug 2019 14:56:57 -0700 Message-ID: References: <20190822030739.GH9017@brightrain.aerifal.cx> <87k1b4rmh3.fsf@oldenburg2.str.redhat.com> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000c90ac005910c3c5b" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="64950"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Rich Felker To: musl@lists.openwall.com Original-X-From: musl-return-14613-gllmg-musl=m.gmane.org@lists.openwall.com Mon Aug 26 23:57:30 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1i2MzS-000Gjf-Ee for gllmg-musl@m.gmane.org; Mon, 26 Aug 2019 23:57:30 +0200 Original-Received: (qmail 16343 invoked by uid 550); 26 Aug 2019 21:57:21 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 16324 invoked from network); 26 Aug 2019 21:57:20 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pRiuqd6zsrhM//mjIGdlpVql+0qI4dAACZmG1SKcJ5I=; b=EI+ykfv5MF4adxofCzEjummvVw6e6LTb8m6gmpgy8LnNQ9Cf+DAEL+EVadkj206nAc A4aic+eLq3t3NKDD3bYPzUFUcfvhBKUJ4Sm+t27Lm7eejGHkxJlNG79rIKiUXnd0I2c5 rST47+AsV++GyZIO0Oq9Tr7nRWTv1bOrRYV8BgZHpDh61n58sHGaopc56gmqsEG3VwXj L0nSh8/fgvEreoJ6EKTM2sXQOXcRvGqjLD7PdftuH1aVJMGyycN0QyAoesSJ6wZEEXgT Z11hjEgUem9KOBS8mJ8ij4/JKIQ7TkJQ5SKcXxZ3XZ9Fog4Qs2M0snGnb2K2dEMi0wuq 3ghA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pRiuqd6zsrhM//mjIGdlpVql+0qI4dAACZmG1SKcJ5I=; b=I4Hd1k+5RvxGlP8l9gSZzw3fRikBLI50ms1NBdr2UEre0RWYS+qi0B6S00ENZvuf4a I+ohhTvMhyB1lZ6V+Po6RrhjjGo+F9gflgrKAp2hf7gHCxjbfFtUkgkLslWMosyPbeyl wozP56jHrFSkDvWKtvj1pUyO3krWTvIsh9FP8Lw4555STLbWqTr+64GeRAGXEk4xscRP PSgxrLKIhd7Kd8Z4pYOvGP8zW3eBA2pYWun8qBCPIixRnUXnS+tioblCeJmT48HW8fyX d+O6mUuSSzztSsUIm4z+xE6FmNSQvK5YkPtUyeJLfZU9hzPcn2gsrUGMLIh6kxBlIUZ9 HDGA== X-Gm-Message-State: APjAAAX1YFAL65TZiReXcsSn3bUWqF1RDbXJ7/dKKNNg7brsblsSaw40 iU9SC/ZV/4YVNlNzKYE4F3Pl37w6hRweohP83cMPK2sD5DxbWw== X-Google-Smtp-Source: APXvYqwpXazuq1Z1aEji+gbV3nBJ04xS+MyioPzJpWb2W/aZoNQQ1JaDT4Bp/KTYQJQ0YuchXG3hLAe1EgXYyHjvEq4= X-Received: by 2002:adf:9e09:: with SMTP id u9mr25015166wre.169.1566856628994; Mon, 26 Aug 2019 14:57:08 -0700 (PDT) In-Reply-To: <87k1b4rmh3.fsf@oldenburg2.str.redhat.com> Xref: news.gmane.org gmane.linux.lib.musl.general:14597 Archived-At: --000000000000c90ac005910c3c5b Content-Type: text/plain; charset="UTF-8" Hi all, thank you for your response, I do have a couple of follow-up questions. * Rich Felker: > It "requires" backtrace? For actual operation, or for printing stack > traces in the event of a crash? The latter, but it's not really my place to question that. It works on other platforms, so I'd like to achieve parity. > backtrace should not require any "support from libc"... To be fair, I'm a bit out of my depth here. From what I see, the lib is relying on compiler builtins, and they just just fall on their face. I'm using gcc in both cases, so I'm sure there's some magic involved somewhere, but I really can't tell where. * Florian Weimer: Arch is x86_64, so nothing funky here, and it works on glibc. So, no clue. * Tuan Hoan: > We use libexecinfo, not sure if it helps your case. Thanks for that. I guess my question on that on is: it compiles, but that is actually run without crashing? Again, thank you all for having taken the time to read and reply. -- Guillaume Quintard --000000000000c90ac005910c3c5b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

tha= nk you for your response, I do have a couple of follow-up questions.
<= div>
* Rich Felker:
=

> It "requires" backtrace? For actual operation, or for prin= ting stack
> traces in the eve= nt of a crash?

T= he latter, but it's not really my place to question that. It works on o= ther platforms, so I'd like to achieve parity.
> backtrace should not require any "suppor= t from libc"...

To be fair, I'= ;m a bit out of my depth here. From what I see, the lib is relying on compi= ler builtins, and they just just fall on their face.
I'm usin= g gcc in both cases, so I'm sure there's some magic involved somewh= ere, but I really can't tell where.

* Florian = Weimer:

Arch is x86_64, so nothing funky here, and= it works on glibc. So, no clue.

* Tuan Hoan:

> We use libexecinfo, not sure if it helps your ca= se.

Thanks for that. I guess my question on that o= n is: it compiles, but that is actually run without crashing?

Again, thank you all for having taken the time to read and = reply.

--
Guillaume Quintard
--000000000000c90ac005910c3c5b--