From: Guillaume Quintard <guillaume.quintard@gmail.com>
To: musl@lists.openwall.com
Cc: Rich Felker <dalias@libc.org>
Subject: Re: libexecinfo with musl
Date: Mon, 26 Aug 2019 14:56:57 -0700 [thread overview]
Message-ID: <CAOrPor=7i-vi8G+ObFBN6GoYsdgBGdmMh4p9a+ExqqJG4e6eeQ@mail.gmail.com> (raw)
In-Reply-To: <87k1b4rmh3.fsf@oldenburg2.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1646 bytes --]
next prev parent reply other threads:[~2019-08-26 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 0:32 Guillaume Quintard
2019-08-22 3:07 ` Rich Felker
2019-08-23 14:21 ` Florian Weimer
2019-08-26 21:56 ` Guillaume Quintard [this message]
2019-08-28 8:06 ` Tuan Hoang
2019-08-28 19:07 ` Guillaume Quintard
2019-08-22 17:17 ` Tuan Hoang
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='CAOrPor=7i-vi8G+ObFBN6GoYsdgBGdmMh4p9a+ExqqJG4e6eeQ@mail.gmail.com' \
--to=guillaume.quintard@gmail.com \
--cc=dalias@libc.org \
--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).