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 gdb/30340] gdb.base/watchpoint-unaligned.exp produces TCL error
Date: Fri, 14 Apr 2023 10:55:29 +0000	[thread overview]
Message-ID: <bug-30340-4717-2qr0Oy2UWH@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 #9 from Alexandra Hájková <ahajkova at redhat dot com> ---
(In reply to Luis Machado from comment #8)
> Thanks!
> 
> The ptrace requests for the debug registers seem to be going through just
> fine:
> 
> ptrace(PTRACE_GETREGSET, 1832792, NT_ARM_HW_WATCH, {iov_base=0xffffc0ea3b88,
> iov_len=264}) = 0
> 
> ptrace(PTRACE_GETREGSET, 1832792, NT_ARM_HW_BREAK, {iov_base=0xffffc0ea3b88,
> iov_len=264}) = 0
> 
> I think this rules out permissions issues with ptrace, and we're back at
> suspecting the architecture level comparisons.
> 
> Since you have ready access to the hardware, would you mind running a quick
> check on your side?
> 
> In gdb/nat/aarch64-linux-hw-point.c:compatible_debug_arch, could you please
> add a warning statement printing the debug_arch? Like we do for example in
> aarch64_linux_get_debug_reg_capacity when printing the number of
> watchpoints/breakpoints.
> 
> Then rebuild gdb, run the test (to create the test executable) and attempt
> to run that same command line we used for strace.
> 
> Could you then paste the architecture level that is printed?
> 
> Also, could you please paste the output of "cat /proc/cpuinfo"?
> 
> Thanks!

I'm getting 0 for the debug_arch.

as for the cpuinfo:
processor       : 0
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

processor       : 1
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

processor       : 2
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

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

Should I update my patch to check for any warnings/errors or do you just want
to take care of this issue yourself?

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

  parent reply	other threads:[~2023-04-14 10:55 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 [this message]
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
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-2qr0Oy2UWH@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).