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] New: [ppc64] gdb/infrun.c:2529: internal-error: void resume_1(gdb_signal): Assertion `!(thread_has_single_step_breakpoints_set (tp) && step)' failed
Date: Thu, 12 Nov 2020 23:44:57 +0000	[thread overview]
Message-ID: <bug-26873-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26873
           Summary: [ppc64] gdb/infrun.c:2529: internal-error: void
                    resume_1(gdb_signal): Assertion
                    `!(thread_has_single_step_breakpoints_set (tp) &&
                    step)' failed
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Consider the test-case gdb.threads/watchthreads-threaded.exp from
https://src.fedoraproject.org/rpms/gdb/blob/master/f/gdb-6.3-threaded-watchpoints2-20050225.patch
.

On ppc64 and ppc64le, on Factory, we run into:
...
Old value = 1^M
New value = 2^M
thread_function (arg=0x2) at watchthreads-threaded.c:61^M
61              (*myp) ++; usleep (1); /* Loop increment.  */^M
(gdb) continue^M
Continuing.^M
../../gdb/infrun.c:2529: internal-error: void resume_1(gdb_signal): Assertion
`!(thread_has_single_step_breakpoints_set (tp) && step)' failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
Quit this debugging session? (y or n)
FAIL: gdb.threads/watchthreads-threaded.exp: threaded watch loop (GDB internal
error)
...

This was using an opensuse package build & test on obs, using 10.1 sources and
fedora patches.  There's nothing powerpc-specific in the fedora patch set, so
I'm assuming this can be reproduced with trunk as well.

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

             reply	other threads:[~2020-11-12 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 23:44 vries at gcc dot gnu.org [this message]
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
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@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).