From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BF88D3858C2F; Mon, 17 Apr 2023 13:33:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BF88D3858C2F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681738433; bh=FW3DGpoaD6i5dPrX95/c15AwIV60ubafYsBDbXo2zR0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ClBQwwAkBxzYjyM7I2QtyB0xv3ug2Vk0tUjnh68Vhf1TlfTix1DAUXsPp5YOYckum k3o/Nj4D76NCh3rIoUEtyXjRWpzhQuuPCTfusOHTUIzUglIqsbZy8FGn1+iHzWhzot pUM7W/a09LG3Teku/jTYO/J9Cycy53EqfiKE4mg4= From: "ahajkova at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/30340] [gdb/aarch64] gdb doesn't handle unknown debug architecture versions gracefully (TCL errors on gdb.base/watchpoint-unaligned.exp with KVM) Date: Mon, 17 Apr 2023 13:33:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ahajkova at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: luis.machado at arm dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30340 --- Comment #20 from Alexandra H=C3=A1jkov=C3=A1 --- (In reply to Luis Machado from comment #1) > I think what you want is to check for any warnings/errors when attempting= to > create hardware watchpoints/breakpoints and then fail and abort testing. >=20 > For example, gdb emits these warnings: >=20 > warning: Unable to determine the number of hardware watchpoints available. > warning: Unable to determine the number of hardware breakpoints available. >=20 > They should be an indication something is off, and there is no point > resuming testing in that case. those warnings seems to be emmited when runto_main is called --=20 You are receiving this mail because: You are on the CC list for the bug.=