public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/30340] [gdb/aarch64] gdb doesn't handle unknown debug architecture versions gracefully (TCL errors on gdb.base/watchpoint-unaligned.exp with KVM) Date: Tue, 02 May 2023 09:38:24 +0000 [thread overview] Message-ID: <bug-30340-4717-3BytPi1IgE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30340-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30340 Andrew Burgess <aburgess at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW CC| |aburgess at redhat dot com --- Comment #26 from Andrew Burgess <aburgess at redhat dot com> --- We've discussed this bug a little on IRC, but I wanted to drop a note of the current plan. I feel there's two issues here, one if the TCL error. This occurs because a TCL variable ends up not being initialized when one of the gdb_test_multiple calls fails. Then there's a different (but related) question of why the gdb_test_multiple call failed. I think we should fix the uninitialized variable issue separately to digging into the question of "why" the test is failing. There are many reasons why a gdb_test_multiple call could fail - even if we spot and catch this specific case, the gdb_test_multiple could fail for some other reason tomorrow, and then the TCL error would be back. Alexandra has a patch on the list which addresses the TCL issue which we can merge sooner rather than later[1]. As for why the test is failing in this case, it appears to be some ptrace call that is returning unexpected results. Right now it's not clear if this is a legitimate result that GDB/the testsuite is just not expecting, or if this unexpected result represents a bug in the software stack -- the issue was seen on a virtual machine using Red Hat modified .... well ... everything -- and everything is of various ages. We're currently digging into this issue within RH trying to figure out where the unexpected result is coming from, and will update here once we know more information. [1] https://sourceware.org/pipermail/gdb-patches/2023-April/199092.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-02 9:38 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 20:57 [Bug gdb/30340] New: gdb.base/watchpoint-unaligned.exp produces TCL error 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 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 [this message] 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-3BytPi1IgE@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).