[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190123005701.GU23599@brightrain.aerifal.cx>
Date: Tue, 22 Jan 2019 19:57:01 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Possibly spurious EAGAIN seen in pthread_key_create on x86
On Tue, Jan 22, 2019 at 03:15:35PM -0600, A. Wilcox wrote:
> Hello there muslers,
>
> While running the test suite for GLib++ (the C++ wrapper for GLib) on
> our 32-bit x86 builder (i686), after upgrading to 1.1.21, it logged:
>
>
> FAIL: glibmm_mainloop/test
> ==========================
> GLib (gthread-posix.c): Unexpected error from C library during
> 'pthread_key_create': Resource temporarily unavailable. Aborting.
>
>
> Running the test suite an additional 160 (one hundred and sixty) times
> could not repeat the result. Still, I wanted to report it on the
> off-chance there is some significance to this single result.
>
> Importantly, I haven't noticed this failure on any of the other
> architectures we've built GLib++ on (ppc32, ppc64, aarch64).
Can you figure out what this test is doing, or point to source so
others can? My best guess is that it's creating and destroying keys
very many times, and something happened that caused the dirty-slot
reclaiming __synccall to fail (maybe EMFILE or ENFILE?).
Rich
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.
