From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 798AF3858D39; Wed, 17 May 2023 11:30:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 798AF3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684323053; bh=L2eeLdrK6OdigQLtJnAnfKBo4e23zY729UrJvH7AOqw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yHPNjhXBkt1+cY83vs2dFqqrPlvcPTkZ1ExYmIQNS2jh3JRrPeOcSNZLyHDxbu0XB P6KVxYANaOKxDdSIp/WDKZ1Wbkzs6qs0z40xVRUJ1d5THMwFcDB4xFlWRDrWlbcQkx f/3A3NqRexgy0DrIrm+ue91xT/bn0IYf3fchRa2c= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109889] [13/14 Regression] Segfault in __run_exit_handlers since r13-5309-gc3c6c307792026 Date: Wed, 17 May 2023 11:30:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.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://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109889 --- Comment #4 from Jonathan Wakely --- (In reply to Jakub Jelinek from comment #2) > r2 is the toc pointer, so having it 0 is weird. > Looking at glibc-2.36-10.fc37 (not sure if you are using a different one)= , I glibc-2.36-9.fc37.ppc64le > see > 000000000005b560 <__run_exit_handlers>: > 5b560: 21 00 4c 3c addis r2,r12,33 > 5b564: a0 b9 42 38 addi r2,r2,-18016 > ... > 5b5a8: 18 00 41 f8 std r2,24(r1) > so wonder what x/1gx $r1+24 is. (gdb) x/1gx $r1+24 0x7fffffffe8d8: 0x0000000000000000=