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: Fri, 29 Oct 2021 06:25:28 +0000	[thread overview]
Message-ID: <bug-28355-4717-923QIokQTD@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 #20 from sourceware at johnea dot net ---
Just confirming that gdbserver 9.2 on archlinux aarch64 rootfs does work
correctly, and the problem is reproducible on gdbserver 11.1.

Thanks for that tip!

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

  parent reply	other threads:[~2021-10-29  6:25 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
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 [this message]
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-923QIokQTD@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).