From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8D91A385840D; Tue, 30 Jan 2024 14:33:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8D91A385840D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1706625206; bh=GRejHkkC8KQF50Bw/h+OLqC/OuqA7/LRJsRTJFVzhik=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j0ZgmTPD6xZn2HkM+xipj28mJlPSoAc1ZUFatJgbSyVHfG3Lqat6NFCJ9VGttwVbC udBcH6sfJQycacst78YuSMSChlro23YuCPWxYHA19cySGDpBN0h5t9qrH+rQK9Lt2W /2tgwVGfr4WI8paRlueTx91mxn6HNT+YvoGpwvnk= From: "blarsen at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug corefiles/31294] gcores do not work in 32-bit arm targets Date: Tue, 30 Jan 2024 14:33:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: corefiles X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: blarsen 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: component short_desc 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=3D31294 Guinevere Larsen changed: What |Removed |Added ---------------------------------------------------------------------------- Component|backtrace |corefiles Summary|cant unwind |gcores do not work in |__libc_do_syscall from |32-bit arm targets |gcore in arm 32 bits | --- Comment #1 from Guinevere Larsen --- The rest of gdb.threads/threadcrash.exp gcore section has even worse result= s. The log for "thread apply all backtrace" is as follows: thread apply all backtrace^M ^M Thread 7 (LWP 776476):^M #0 0xf7eadb04 in ?? ()^M #1 0xf7f13a7e in ?? ()^M Backtrace stopped: previous frame identical to this frame (corrupt stack?)^M ^M Thread 6 (LWP 776475):^M #0 0xf7eadb04 in ?? ()^M #1 0xf7f13a7e in ?? ()^M Backtrace stopped: previous frame identical to this frame (corrupt stack?)^M ^M Thread 5 (LWP 776474):^M #0 0xf7eadb04 in ?? ()^M #1 0xf7f13a7e in ?? ()^M Backtrace stopped: previous frame identical to this frame (corrupt stack?)^M ^M Thread 4 (LWP 776473):^M #0 do_spin_task (location=3DSIGNAL_ALT_STACK) at /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139^M #1 0x00400a5e in signal_handler (signo=3D10) at /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:241^M #2 ^M #3 0xf7eadb06 in ?? ()^M #4 0xf7eed292 in ?? ()^M Backtrace stopped: previous frame identical to this frame (corrupt stack?)^M ^M Thread 3 (LWP 776472):^M #0 do_spin_task (location=3DSIGNAL_HANDLER) at /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139^M #1 0x00400a5e in signal_handler (signo=3D10) at /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:241^M #2 ^M #3 0xf7eadb06 in ?? ()^M #4 0xf7eed292 in ?? ()^M Backtrace stopped: previous frame identical to this frame (corrupt stack?)^M Seems that either the writing or reading of gcores is thoroughly broken. --=20 You are receiving this mail because: You are on the CC list for the bug.=