public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "petemoore at gmx dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29471] gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64-none-elf Date: Fri, 21 Oct 2022 12:42:32 +0000 [thread overview] Message-ID: <bug-29471-4717-X6b7ZNdv0o@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29471-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29471 --- Comment #2 from Pete Moore <petemoore at gmx dot net> --- Many thanks Luis! In one shell, I am running Qemu 7.1.0 from homebrew on macOS, with: ``` $ qemu-system-aarch64 -s -S -M raspi3b -kernel [KERNEL-ELF-FILE] -serial null -serial stdio ``` Then in a separate shell on my mac, I am running gdb under docker with: ``` $ docker run [...OPTIONS...] -ti [MY-DOCKER-IMAGE-CONTAINING-GDB] /path/to/aarch64-none-elf-gdb [KERNEL-ELF-FILE] (gdb) target extended-remote host.docker.internal:1234 ... ``` It sounds like this is an issue with the Qemu gdb target then, and I should raise this issue instead against Qemu 7.1.0 - is that correct? Many thanks! Pete -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-21 12:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-11 12:10 [Bug gdb/29471] New: gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64 petemoore at gmx dot net 2022-08-11 15:07 ` [Bug gdb/29471] gdb 12.1 'i r' command doesn't recognise register NZCV under target aarch64-none-elf petemoore at gmx dot net 2022-10-21 10:06 ` luis.machado at arm dot com 2022-10-21 12:42 ` petemoore at gmx dot net [this message] 2022-10-21 14:30 ` luis.machado at arm dot com 2022-11-03 9:22 ` cvs-commit at gcc dot gnu.org 2022-12-05 15:37 ` luis.machado at arm dot com
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-29471-4717-X6b7ZNdv0o@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).