public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ahajkova at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/29423] [gdb, tdep/aarch64] FAIL: gdb.base/watchpoint-unaligned.exp: continue (timeout) Date: Tue, 11 Apr 2023 16:51:24 +0000 [thread overview] Message-ID: <bug-29423-4717-XlLUoG5vtK@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29423-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29423 Alexandra Hájková <ahajkova at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ahajkova at redhat dot com --- Comment #10 from Alexandra Hájková <ahajkova at redhat dot com> --- When running this test aarch64, Fedora 39: CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x3 CPU part : 0xd0c CPU revision : 1 I'm getting TCL error: root/build/gdb/gdb version 14.0.50.20230411-git -nw -nx -q -iex "set height 0" -iex "set width 0" -data-directory /root/build/gdb/data-directory ERROR: ------------------------------------------- ERROR: in testcase /root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp ERROR: can't read "wpoffset_to_wpnum(1)": no such element in array ERROR: tcl error code TCL READ VARNAME ERROR: tcl error info: can't read "wpoffset_to_wpnum(1)": no such element in array while executing "list -re "\r\nCould not insert hardware watchpoint .*\r\n$gdb_prompt $" { } -re "$rwatch_exp $wpoffset_to_wpnum(1):.*alue = .*\r\n$gdb_prompt $" { ..." ("uplevel" body line 1) invoked from within "uplevel list $subst_code" (procedure "gdb_test_multiple" line 77) invoked from within "gdb_test_multiple $test $test { -re "\r\nCould not insert hardware watchpoint .*\r\n$gdb_prompt $" { } -re "$rwatch_exp $wpoffset_to_wpnum(1):.*alu..." ("foreach" body line 24) invoked from within "foreach wpcount {4 7} { array set wpoffset_to_wpnum {} for {set wpoffset 1} {$wpoffset <= $wpcount} {incr wpoffset} { set test "$rwatch data...." (file "/root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp" line 101) invoked from within "source /root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp" ("uplevel" body line 1) invoked from within "uplevel #0 source /root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp" invoked from within "catch "uplevel #0 source $test_file_name" msg" -------------------------------------------------- === gdb Summary === # of expected passes 142 # of unexpected failures 537 # of unresolved testcases 1 # of paths in test names 1 # of duplicate test names 16 /root/build/gdb/gdb version 14.0.50.20230411-git -nw -nx -q -iex "set height 0" -iex "set width 0" -data-directory /root/build/gdb/data-directory ERROR: ------------------------------------------- ERROR: in testcase /root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp ERROR: can't read "wpoffset_to_wpnum(1)": no such element in array ERROR: tcl error code TCL READ VARNAME ERROR: tcl error info: can't read "wpoffset_to_wpnum(1)": no such element in array while executing "list -re "\r\nCould not insert hardware watchpoint .*\r\n$gdb_prompt $" { } -re "$rwatch_exp $wpoffset_to_wpnum(1):.*alue = .*\r\n$gdb_prompt $" { ..." ("uplevel" body line 1) invoked from within "uplevel list $subst_code" (procedure "gdb_test_multiple" line 77) invoked from within "gdb_test_multiple $test $test { -re "\r\nCould not insert hardware watchpoint .*\r\n$gdb_prompt $" { } -re "$rwatch_exp $wpoffset_to_wpnum(1):.*alu..." ("foreach" body line 24) invoked from within "foreach wpcount {4 7} { array set wpoffset_to_wpnum {} for {set wpoffset 1} {$wpoffset <= $wpcount} {incr wpoffset} { set test "$rwatch data...." (file "/root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp" line 101) invoked from within "source /root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp" ("uplevel" body line 1) invoked from within "uplevel #0 source /root/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.base/watchpoint-unaligned.exp" invoked from within "catch "uplevel #0 source $test_file_name" msg" -------------------------------------------------- make[2]: *** [Makefile:226: do-check-single] Error 1 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-11 16:51 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-28 11:39 [Bug tdep/29423] New: " vries at gcc dot gnu.org 2022-07-28 11:39 ` [Bug tdep/29423] " vries at gcc dot gnu.org 2022-07-28 11:50 ` vries at gcc dot gnu.org 2022-07-28 12:24 ` vries at gcc dot gnu.org 2022-07-28 12:36 ` luis.machado at arm dot com 2022-07-28 12:41 ` vries at gcc dot gnu.org 2022-07-28 12:47 ` luis.machado at arm dot com 2022-07-28 14:15 ` vries at gcc dot gnu.org 2022-07-28 15:25 ` vries at gcc dot gnu.org 2022-07-28 15:26 ` vries at gcc dot gnu.org 2022-07-29 14:23 ` vries at gcc dot gnu.org 2023-04-11 16:51 ` ahajkova at redhat dot com [this message] 2023-04-11 16:52 ` ahajkova at redhat dot com 2023-04-11 22:07 ` luis.machado at arm dot com 2023-04-12 7:51 ` ahajkova at redhat dot com 2023-04-12 8:27 ` luis.machado at arm dot com 2023-04-12 8:27 ` luis.machado at arm dot com 2023-04-12 8:31 ` luis.machado at arm dot com 2023-04-12 12:55 ` ahajkova at redhat dot com 2023-04-12 13:12 ` luis.machado at arm dot com 2023-04-12 13:54 ` luis.machado at arm dot com 2023-04-12 17:12 ` tromey at sourceware dot org 2023-04-12 17:54 ` luis.machado at arm dot com 2023-04-12 20:59 ` ahajkova at redhat dot com 2024-01-05 15:08 ` vries at gcc dot gnu.org 2024-02-20 20:55 ` vries at gcc dot gnu.org 2024-03-14 10:24 ` cvs-commit at gcc dot gnu.org 2024-03-14 10:26 ` vries at gcc dot gnu.org
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-29423-4717-XlLUoG5vtK@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).