Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 15 Feb 2022 11:59:52 -0500
From: Satadru Pramanik <>
To: Rich Felker <>
Subject: Re: Re: musl getaddr info breakage on older kernels

On Mon, Feb 14, 2022 at 5:00 PM Rich Felker <> wrote:

> Note: you dropped the list from CC in your last reply; I've re-added
> it and bounced your message to the list.
> Mea culpa!

> > When I ran that, I got this:
> > .../musl_getaddrinfo_test
> > AF_INET:
> > AF_INET6: 2607:f8b0:4006:80b::200e
> Are you saying it works (resolves correctly) with the above command
> line? If so that's indicative of buggy Docker seccomp.
> I am saying it resolves correctly with the above command line.

Suggestions on what command line I should be using?

> > Is there a static build of i686 gdb built against musl someone has
> > available which might be helpful here?
> gdb should not need to be built against musl to debug programs built
> against musl. Maybe you're just missing debug info?
> This is entirely possible.
I'm building a musl toolchain with this: (which is itself a variant
of your )
My config.mak is generated inside here:

Is there a way to get the debug info for gdb saved into the musl libc, or
should I open an issue just for that on ?

When I package the musl toolchain, I don't see a debug or .debug folder
being kept in the $(OUTPUT) folder.



Content of type "text/html" skipped

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.