public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/26619] [arm] Unexpected error setting breakpoint/watchpoint Date: Wed, 16 Sep 2020 07:11:40 +0000 [thread overview] Message-ID: <bug-26619-4717-IxN6GoLQDa@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26619-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26619 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Luis Machado from comment #1) > I'm aware of various hardware watchpoint issues for arm 32-bit. I think this > is one of the manifestations. It depends on the kernel version as well, > since there has been fixes to the kernel. > I see. It also happens on Factory though, where I'd expect a reasonably up-2-date kernel. > What exact hardware is this by the way? I'm not sure, it's OBS and AFAICT from the log it's KVM/QEMU. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-16 7:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-15 15:13 [Bug breakpoints/26619] New: " vries at gcc dot gnu.org 2020-09-15 15:14 ` [Bug breakpoints/26619] " vries at gcc dot gnu.org 2020-09-15 15:32 ` luis.machado at linaro dot org 2020-09-16 7:11 ` vries at gcc dot gnu.org [this message] 2024-04-23 0:58 ` thiago.bauermann at linaro dot org 2024-04-23 7:39 ` luis.machado at arm dot com 2024-04-23 18:44 ` thiago.bauermann at linaro dot org 2024-04-24 0:13 ` thiago.bauermann at linaro dot org 2024-04-24 17:47 ` thiago.bauermann at linaro dot org 2024-04-24 21:11 ` vries at gcc dot gnu.org 2024-04-25 13:59 ` 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-26619-4717-IxN6GoLQDa@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).