Date: Thu, 22 Aug 2019 19:17:37 +0200 From: Tuan Hoang <tmhoang@...ux.ibm.com> To: musl@...ts.openwall.com Subject: Re: libexecinfo with musl We use libexecinfo, not sure if it helps your case. https://git.alpinelinux.org/aports/tree/main/s390-tools/APKBUILD#n49 https://git.alpinelinux.org/aports/tree/main/libexecinfo/APKBUILD On 8/22/19 1:32 AM, Guillaume Quintard wrote: > Hi, > > Apologies if this has already been answered before, information is a bit > hard to find on the topic. > > This is what brings me here: > https://github.com/mikroskeem/libexecinfo/issues/2 > > I'm trying to build and run a bigger program (varnish) that requires > backtrace(), and while it compiles, executing backtrace() results in a > segfault. It looks like the function __builtin_frame_address doesn't > really do what it should. > > It's apparently a builtin function from the compiler, but I sort of > understood it also requires some support from the libc. If that's the > case, would someone care to explain the specifics to help us decide if > we should just cut the backtrace() feature from varnish on musl, or if > we should work towards feature parity. > > Thanks! > > -- > Guillaume Quintard
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.