public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30340] gdb.base/watchpoint-unaligned.exp produces TCL error Date: Fri, 14 Apr 2023 12:09:30 +0000 [thread overview] Message-ID: <bug-30340-4717-VHoeNsj5Rq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30340-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30340 --- Comment #10 from Luis Machado <luis.machado at arm dot com> --- Hi Alexandra. Thanks for the info. I think hardening the test to make sure it doesn't test things that are known to not work is useful still. With that said, I think we're dealing with a different issue for this particular AArch64 machine. Here's your output from cpuinfo: processor : 3 BogoMIPS : 50.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x3 CPU part : 0xd0c CPU revision : 1 Here's an output from a Ampere Mt Snow I have access to: processor : 159 BogoMIPS : 50.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x3 CPU part : 0xd0c CPU revision : 1 They are the same, so technically things should work. But you're getting 0 for the debug arch value, which is invalid. I'll have to do some research on this one. Do you know how this machine is set? Is it a standalone machine or part of a cloud setup? Are there security features enabled? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-14 12:09 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 20:57 [Bug gdb/30340] New: " ahajkova at redhat dot com 2023-04-13 7:47 ` [Bug gdb/30340] " luis.machado at arm dot com 2023-04-13 13:28 ` luis.machado at arm dot com 2023-04-13 13:52 ` ahajkova at redhat dot com 2023-04-13 14:01 ` luis.machado at arm dot com 2023-04-13 17:39 ` ahajkova at redhat dot com 2023-04-13 17:39 ` ahajkova at redhat dot com 2023-04-13 17:41 ` ahajkova at redhat dot com 2023-04-14 9:55 ` luis.machado at arm dot com 2023-04-14 9:56 ` luis.machado at arm dot com 2023-04-14 10:55 ` ahajkova at redhat dot com 2023-04-14 12:09 ` luis.machado at arm dot com [this message] 2023-04-14 13:58 ` luis.machado at arm dot com 2023-04-14 15:03 ` ahajkova at redhat dot com 2023-04-14 16:31 ` luis.machado at arm dot com 2023-04-14 19:00 ` ahajkova at redhat dot com 2023-04-17 8:25 ` luis.machado at arm dot com 2023-04-17 8:25 ` luis.machado at arm dot com 2023-04-17 9:16 ` ahajkova at redhat dot com 2023-04-17 9:25 ` ahajkova at redhat dot com 2023-04-17 9:32 ` luis.machado at arm dot com 2023-04-17 9:33 ` [Bug gdb/30340] [gdb/aarch64] gdb doesn't handle unknown debug architecture versions gracefully (TCL errors on gdb.base/watchpoint-unaligned.exp with KVM) luis.machado at arm dot com 2023-04-17 13:33 ` ahajkova at redhat dot com 2023-04-18 7:59 ` luis.machado at arm dot com 2023-04-18 11:47 ` [Bug tdep/30340] " luis.machado at arm dot com 2023-04-18 13:27 ` luis.machado at arm dot com 2023-04-18 13:28 ` luis.machado at arm dot com 2023-04-18 19:59 ` ahajkova at redhat dot com 2023-04-18 20:05 ` ahajkova at redhat dot com 2023-05-02 9:38 ` aburgess at redhat dot com 2023-05-02 9:41 ` aburgess at redhat dot com 2023-05-02 20:51 ` cvs-commit at gcc dot gnu.org 2023-05-09 10:01 ` luis.machado at arm dot com 2023-05-09 10:01 ` luis.machado at arm dot com 2023-05-15 10:02 ` aburgess at redhat dot com 2023-07-05 14:28 ` brobecker at gnat dot com 2023-07-05 14:28 ` brobecker at gnat dot com 2023-07-05 14:31 ` 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-30340-4717-VHoeNsj5Rq@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).