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/26873] [ppc64] gdb/infrun.c:2529: internal-error: void resume_1(gdb_signal): Assertion `!(thread_has_single_step_breakpoints_set (tp) && step)' failed
Date: Wed, 28 Sep 2022 12:14:51 +0000	[thread overview]
Message-ID: <bug-26873-4717-VMCfZDZa96@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26873-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26873

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 14362
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14362&action=edit
gdb-ppc64le-suse-linux-m64.log

Reproduced again, with gdb 12.1 based package.

Note that the first sign of trouble is:
...
(gdb) PASS: gdb.threads/watchthreads-threaded.exp: get initial args3
watch args[2]^M
Hardware watchpoint 3: args[2]^M
(gdb) PASS: gdb.threads/watchthreads-threaded.exp: watch args[2]
watch args[3]^M
Watchpoint 4: args[3]^M
(gdb) FAIL: gdb.threads/watchthreads-threaded.exp: watch args[3]
...

The test-case expects two hardware watchpoints, but gets one hardware and one
software watchpoint.

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

  parent reply	other threads:[~2022-09-28 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 23:44 [Bug breakpoints/26873] New: " vries at gcc dot gnu.org
2020-12-10 10:31 ` [Bug breakpoints/26873] " vries at gcc dot gnu.org
2022-09-28 12:14 ` vries at gcc dot gnu.org [this message]
2022-09-28 12:34 ` 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-26873-4717-VMCfZDZa96@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).