[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878sifrdo0.fsf@mid.deneb.enyo.de>
Date: Tue, 28 Apr 2020 14:35:27 +0200
From: Florian Weimer <fw@...eb.enyo.de>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: Michael Kerrisk <mtk.manpages@...il.com>,
libc-alpha <libc-alpha@...rceware.org>,
carlos <carlos@...hat.com>, Rich Felker <dalias@...c.org>,
linux-api <linux-api@...r.kernel.org>,
Boqun Feng <boqun.feng@...il.com>,
Will Deacon <will.deacon@....com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ben Maurer <bmaurer@...com>, Dave Watson <davejwatson@...com>,
Thomas Gleixner <tglx@...utronix.de>,
Paul <paulmck@...ux.vnet.ibm.com>, Paul Turner <pjt@...gle.com>,
Joseph Myers <joseph@...esourcery.com>,
Szabolcs Nagy <szabolcs.nagy@....com>
Subject: Re: [PATCH glibc 5/9] glibc: Perform rseq(2) registration at C startup and thread creation (v17)
* Mathieu Desnoyers:
> One issue I'm currently facing when running "make check": because
> nptl/tst-rseq-nptl.c uses pthread_cancel(), I run into an Abort
> with:
>
> libgcc_s.so.1 must be installed for pthread_cancel to work
> Didn't expect signal from child: got `Aborted'
This is really unusual. Is the affected test statically linked?
Powered by blists - more mailing lists