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 corefiles/31294] gcores do not work in 32-bit arm targets
Date: Tue, 30 Jan 2024 14:33:24 +0000	[thread overview]
Message-ID: <bug-31294-4717-mXDcV3fDYv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31294-4717@http.sourceware.org/bugzilla/>

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

Guinevere Larsen <blarsen at redhat dot com> 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 <blarsen at redhat dot com> ---
The rest of gdb.threads/threadcrash.exp gcore section has even worse results.
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=SIGNAL_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=10) at
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:241^M
#2  <signal handler called>^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=SIGNAL_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=10) at
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:241^M
#2  <signal handler called>^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.

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

  reply	other threads:[~2024-01-30 14:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 15:25 [Bug backtrace/31294] New: cant unwind __libc_do_syscall from gcore in arm 32 bits blarsen at redhat dot com
2024-01-30 14:33 ` blarsen at redhat dot com [this message]
2024-01-30 14:36 ` [Bug corefiles/31294] gcores do not work in 32-bit arm targets 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-mXDcV3fDYv@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).