From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 985CD385841D; Tue, 27 Jun 2023 16:02:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 985CD385841D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1687881737; bh=B3Ke4iUW9YC46WhcVlMP8j60kN8imP3bxH7/yHXH1WI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=l1X0EE2Ud42EoNPFExVJS+vOi6t7xEmJ01w0IH/3KhNCaa/49eJsdNJnTGv/cyCT3 ceF59cT2x5wh+Gop9BkmueIBhfRYuNLZBbGrtsYhRWuIleR+YI+LYk9NmmoMreEQoD uo+RgE1H2q4xJ3OyhsGouZO8Xb28zzeN5kj+6ris= From: "fberat at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/30587] FAIL: nptl/tst-cleanupx4 on hppa Date: Tue, 27 Jun 2023 16:02:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fberat at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30587 --- Comment #4 from Fr=C3=A9d=C3=A9ric B=C3=A9rat --- Since I don't have the access yet, I'm looking at the logs: test 0 clh (2) global =3D 2, expected 15 This executes fn2(), which should basically do: pthread_cleanup_push (clh, (void *) 3l); _pthread_cleanup_push (&b, clh, (void *) 2l); pthread_cleanup_push (clh, (void *) 1l); Whereas, from the output, only `_pthread_cleanup_pop (&b, 1);` seems to be executed. The same goes for the following iterations. It looks like only _pthread_cleanup_pop actions get executed on cancellation. I don't see how this could be induced by the aforementioned patch. --=20 You are receiving this mail because: You are on the CC list for the bug.=