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:41:53 +0000	[thread overview]
Message-ID: <bug-30340-4717-N4rF3yRZ27@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 #27 from Andrew Burgess <aburgess at redhat dot com> ---
Created attachment 14859
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14859&action=edit
Test program that exposes the problematic ptrace call

Here's the demo program that I've been using to expose the ptrace issue.  The
issue is that when we ask for the H/W watchpoint information we get back a
dbg_info field containing 0 for the architecture field.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-05-02  9:41 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
2023-05-02  9:41 ` aburgess at redhat dot com [this message]
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-N4rF3yRZ27@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: link
Be 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).