public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
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	[thread overview]
Message-ID: <bug-31294-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31294

            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 
* 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=NORMAL) 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=SIGNAL_HANDLER) 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=SIGNAL_ALT_STACK)
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 
* 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=NORMAL) 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=SIGNAL_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=SIGNAL_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 fail
the unwinding. This can be shown in the Linaro CI bug GNU-1120[1], even though
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

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-01-25 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 15:25 blarsen at redhat dot com [this message]
2024-01-30 14:33 ` [Bug corefiles/31294] gcores do not work in 32-bit arm targets blarsen at redhat dot com
2024-01-30 14:36 ` sam at gentoo dot org
2024-01-31  3:54 ` thiago.bauermann at linaro dot org
2024-02-01 19:12 ` thiago.bauermann at linaro dot org
2024-03-11 23:01 ` thiago.bauermann at linaro dot org
2024-03-12  7:04 ` vries at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31294-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).