public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "thiago.bauermann at linaro dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug corefiles/31294] gcores do not work in 32-bit arm targets Date: Wed, 31 Jan 2024 03:54:13 +0000 [thread overview] Message-ID: <bug-31294-4717-bWB4oiSegf@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31294-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31294 Thiago Jung Bauermann <thiago.bauermann at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thiago.bauermann at linaro dot org --- Comment #2 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> --- I'm currently looking into bug #31254 which has similar symptoms. I narrowed the problem in that bug down to the "arm exidx" unwinder, which uses C++ exception tables to unwind frames. I think there's a memory corruption issue with one of its data structures. I'm hoping to have more information tomorrow. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-31 3:54 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 ` [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 [this message] 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-bWB4oiSegf@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: linkBe 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).