public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sourceware at johnea dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/28355] [aarch64] regcache.cc:257: A problem internal to GDBserver has been detected. Unknown register tag_ctl requested Date: Thu, 28 Oct 2021 22:09:30 +0000 [thread overview] Message-ID: <bug-28355-4717-x6cDudUhq8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28355-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28355 --- Comment #17 from sourceware at johnea dot net --- OK, one slight twist. The failure occurs on an archlinuxarm rootfs, with gdbserver 11.1. When I boot into Xilinx's petalinux rootfs, remote debug works correctly, with gdbserver 9.2. In both cases the x86 host runs aarch64-linux-gnu-gdb 11.1. The data asked for, from both platforms: >From aarch64 petalinux command line: # LD_SHOW_AUXV=1 /bin/true AT_SYSINFO_EHDR: 0xffffaf62c000 AT_??? (0x33): 0x1270 AT_HWCAP: 8fb AT_PAGESZ: 4096 AT_CLKTCK: 100 AT_PHDR: 0xaaaaddbb0040 AT_PHENT: 56 AT_PHNUM: 9 AT_BASE: 0xffffaf5fb000 AT_FLAGS: 0x0 AT_ENTRY: 0xaaaaddbb1740 AT_UID: 0 AT_EUID: 0 AT_GID: 0 AT_EGID: 0 AT_SECURE: 0 AT_RANDOM: 0xffffd9b84c38 AT_HWCAP2: 0x0 AT_EXECFN: /bin/true AT_PLATFORM: aarch64 >From aaarch64 archlinuxarm command line: # LD_SHOW_AUXV=1 /bin/true AT_SYSINFO_EHDR: 0xffffa2f68000 AT_??? (0x33): 0x1270 AT_HWCAP: 8fb AT_PAGESZ: 4096 AT_CLKTCK: 100 AT_PHDR: 0xaaaae9850040 AT_PHENT: 56 AT_PHNUM: 9 AT_BASE: 0xffffa2f37000 AT_FLAGS: 0x0 AT_ENTRY: 0xaaaae98516c8 AT_UID: 0 AT_EUID: 0 AT_GID: 0 AT_EGID: 0 AT_SECURE: 0 AT_RANDOM: 0xffffc9115218 AT_HWCAP2: 0x0 AT_EXECFN: /bin/true AT_PLATFORM: aarch64 The gdb output was captured by setting: (gdb) set logging debugredirect on (gdb) set logging on (gdb) set debug remote 1 (gdb) set debug remote-packet-max-chars -1 (gdb) target remote zcu102:1234 When using the archlinuxarm rootfs, gdbserver 11.1, the (gdb) target remote command led to immediate crash of gdbserver on the target. Data attached as: gdbserver-11.1-archlinuxarm-failed.txt.gz When using the petalinux rootfs, gdbserver 9.2, files and libraries were read as expected, and I continued to set breakpoints, single step, and the hello application ran and terminated successfully. Data attached as: gdbserver-9.2-petalinux-pass.txt.gz Don't be fooled by the filenames, both of these captures occurred on the same x86 host, running aarch64-linux-gnu-gdb 11.1. The names represent the rootfs and gdbserver version on the remote target. Don't know if it's related, but I was also unable to get tcf-agent working on the archlinuxarm rootfs, whereas it works on the petalinux rootfs. I'd actually prefer to run the archlinux aarch64 rootfs, and I hope this data capture can help illuminate the bug, and lead to a fix. Please let me know if I can capture more data, or test updates... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-28 22:09 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-20 13:28 [Bug tdep/28355] New: " vries at gcc dot gnu.org 2021-09-20 13:28 ` [Bug tdep/28355] " vries at gcc dot gnu.org 2021-09-20 14:00 ` luis.machado at linaro dot org 2021-09-20 14:27 ` luis.machado at linaro dot org 2021-09-20 14:30 ` luis.machado at linaro dot org 2021-09-21 12:48 ` luis.machado at linaro dot org 2021-09-27 10:00 ` vries at gcc dot gnu.org 2021-10-01 11:44 ` luis.machado at linaro dot org 2021-10-06 12:04 ` vries at gcc dot gnu.org 2021-10-06 12:06 ` vries at gcc dot gnu.org 2021-10-06 12:07 ` luis.machado at linaro dot org 2021-10-06 12:07 ` vries at gcc dot gnu.org 2021-10-28 17:05 ` sourceware at johnea dot net 2021-10-28 17:10 ` luis.machado at linaro dot org 2021-10-28 17:24 ` luis.machado at linaro dot org 2021-10-28 17:31 ` sourceware at johnea dot net 2021-10-28 17:59 ` luis.machado at linaro dot org 2021-10-28 17:59 ` luis.machado at linaro dot org 2021-10-28 19:46 ` luis.machado at linaro dot org 2021-10-28 19:46 ` luis.machado at linaro dot org 2021-10-28 22:04 ` sourceware at johnea dot net 2021-10-28 22:06 ` sourceware at johnea dot net 2021-10-28 22:09 ` sourceware at johnea dot net [this message] 2021-10-29 0:34 ` luis.machado at linaro dot org 2021-10-29 0:34 ` luis.machado at linaro dot org 2021-10-29 2:12 ` luis.machado at linaro dot org 2021-10-29 6:25 ` sourceware at johnea dot net 2021-10-29 12:47 ` luis.machado at linaro dot org 2021-10-29 18:00 ` luis.machado at linaro dot org 2021-10-29 18:00 ` luis.machado at linaro dot org 2021-10-29 21:45 ` sourceware at johnea dot net 2021-11-01 13:34 ` luis.machado at linaro dot org 2021-11-01 13:34 ` luis.machado at linaro dot org 2021-11-03 13:04 ` cvs-commit at gcc dot gnu.org 2021-11-03 13:05 ` luis.machado at linaro dot org 2021-11-03 14:46 ` sourceware at johnea dot net
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-28355-4717-x6cDudUhq8@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).