public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "thiago.bauermann at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/26619] [arm] Unexpected error setting breakpoint/watchpoint
Date: Wed, 24 Apr 2024 00:13:03 +0000	[thread overview]
Message-ID: <bug-26619-4717-GslNnIAQ9z@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 #6 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> ---
The testcases which ran into that "Unexpected error setting breakpoint: No
such device." in my gdb.log file where:

- gdb.base/break-idempotent.exp
- gdb.base/break-unload-file.exp
- gdb.base/breakpoint-in-ro-region.exp
- gdb.base/hbreak.exp
- gdb.base/hbreak2.exp
- gdb.python/py-breakpoint.exp
- gdb.threads/watchpoint-fork.exp

I updated that QEMU arm TCG VM to Debian 12 (bookworm) and installed the
newest kernel from Debian unstable, which is 6.7.9-armmp-lpae.

Now none of the tests above have that failure. But gdb.base/hbreak.exp has
a different failure now:

Continuing.
Unexpected error setting breakpoint: Invalid argument.
(gdb) FAIL: gdb.base/hbreak.exp: continue to break-at-exit after hbreak

I also see this failure on real hardware with armv8l-linux and Ubuntu's
5.4.0-131-generic kernel. This looks like a different issue.

All the other tests are passing. I'll leave them running in a loop
overnight to confirm (since not all log files from the old testsuite runs
on that machine show this problem).

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

  parent reply	other threads:[~2024-04-24  0:13 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
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 [this message]
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-GslNnIAQ9z@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).