From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E8179385841F; Thu, 25 Jan 2024 15:25:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E8179385841F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1706196300; bh=PKW5DxURPI8oe4PXjbF0BiyJI3m7b66PrDYHX/ToOaU=; h=From:To:Subject:Date:From; b=ep6Hgp+hH/e7pwraLEca6DT8mAL9gLqTRBwxj3K6Y4VA6330tCEey2hPg3KfZnDG8 3xW4GsYVGkuEYbEzR3tGVxvkQZUfPjpwCU+l4upzOGgD1Cx1L6Jmf3csEmQ1teGCGI ClkhmYgXZZYcHfMqBRDcgUn7zDjvdZMs+JlKobF4= From: "blarsen at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug backtrace/31294] New: cant unwind __libc_do_syscall from gcore in arm 32 bits Date: Thu, 25 Jan 2024 15:25:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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 Bug ID: 31294 Summary: cant unwind __libc_do_syscall from gcore in arm 32 bits Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: backtrace Assignee: unassigned at sourceware dot org Reporter: blarsen at redhat dot com Target Milestone: --- The newly introduced test gdb.threads/threadcrash.exp has revealed a pre-existing issue in 32 bit arm. using "info threads" on a regular corefile gives the following thread list: info threads Id Target Id Frame=20 * 1 Thread 0xf7dbe7e0 (LWP 476389) 0x00830cea in crash_function () at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:381 2 Thread 0xf7c6f3a0 (LWP 476390) do_spin_task (location=3DNORMAL) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139 3 Thread 0xf746e3a0 (LWP 476391) do_spin_task (location=3DSIGNAL_HANDL= ER) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139 4 Thread 0xf6c6d3a0 (LWP 476392) do_spin_task (location=3DSIGNAL_ALT_S= TACK) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139 5 Thread 0xf52fe3a0 (LWP 476395) __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 6 Thread 0xf646c3a0 (LWP 476393) __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 7 Thread 0xf5aff3a0 (LWP 476394) __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 Whereas the same command when loading a gcore yields: info threads Id Target Id Frame=20 * 1 LWP 476440 0x00400cea in crash_function () at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:381 2 LWP 476442 do_spin_task (location=3DNORMAL) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139 3 LWP 476443 do_spin_task (location=3DSIGNAL_HANDLER) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139 4 LWP 476444 do_spin_task (location=3DSIGNAL_ALT_STACK) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb= /testsuite/gdb.threads/threadcrash.c:139 5 LWP 476445 0xf7eadb04 in ?? () 6 LWP 476446 0xf7eadb04 in ?? () 7 LWP 476447 0xf7eadb04 in ?? () Notice how the threads are in the same order, and threads 5, 6 and 7 all fa= il the unwinding. This can be shown in the Linaro CI bug GNU-1120[1], even tho= ugh the main focus of the bug is unrelated to this. I'm opening this mostly as a papertrail to add a KFAIL to the test, but it should probably be fixed at some point. [1] https://linaro.atlassian.net/browse/GNU-1120 --=20 You are receiving this mail because: You are on the CC list for the bug.=