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 gdb/29868] New: [gdb, s390x -m31] breakpoint.c:5784: internal-error: bpstat_stop_status_nowatch: Assertion `!target_stopped_by_watchpoint ()'
Date: Sat, 10 Dec 2022 08:18:02 +0000	[thread overview]
Message-ID: <bug-29868-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29868
           Summary: [gdb, s390x -m31] breakpoint.c:5784: internal-error:
                    bpstat_stop_status_nowatch: Assertion
                    `!target_stopped_by_watchpoint ()'
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With current master on s390-linux and target board -unix/-m31, I run into:
...
(gdb) PASS: gdb.threads/watchpoint-fork.exp: parent: singlethreaded:
watchpoints work
continue^M
Continuing.^M
/suse/tdevries/gdb/src/gdb/breakpoint.c:5784: internal-error:
bpstat_stop_status_nowatch: Assertion `!target_stopped_by_watchpoint ()'
failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
----- Backtrace -----^M
FAIL: gdb.threads/watchpoint-fork.exp: parent: singlethreaded: breakpoint after
the first fork (GDB internal error)
...

Backtrace:
...
$ ./show-bt.sh | c++filt 
0x122f20b gdb_internal_backtrace_1^M
        gdb/bt-utils.c:122^M
0x122f30d gdb_internal_backtrace()^M
        gdb/bt-utils.c:168^M
0x1c27655 internal_vproblem^M
        gdb/utils.c:396^M
0x1c27b21 internal_verror(char const*, int, char const*, __va_list_tag*)^M
        gdb/utils.c:476^M
0x25f0d49 internal_error_loc(char const*, int, char const*, ...)^M
        gdbsupport/errors.cc:58^M
0x11e4c2b bpstat_stop_status_nowatch(address_space const*, unsigned long,
thread_info*, target_waitstatus const&)
^M
        gdb/breakpoint.c:5784^M
0x1634877 handle_inferior_event^M
        gdb/infrun.c:5677^M
0x162fddd fetch_inferior_event()^M
        gdb/infrun.c:4202^M
0x16049eb inferior_event_handler(inferior_event_type)^M
        gdb/inf-loop.c:41^M
0x169474f handle_target_event^M
        gdb/linux-nat.c:4205^M
0x25f22a3 handle_file_event^M
        gdbsupport/event-loop.cc:573^M
0x25f2749 gdb_wait_for_event^M
        gdbsupport/event-loop.cc:694^M
0x25f0ff1 gdb_do_one_event(int)^M
        gdbsupport/event-loop.cc:217^M
0x16faa07 start_event_loop^M
        gdb/main.c:411^M
0x16fab99 captured_command_loop^M
        gdb/main.c:471^M
0x16fc8f3 captured_main^M
        gdb/main.c:1330^M
0x16fc989 gdb_main(captured_main_args*)^M
        gdb/main.c:1345^M
0x101affd main^M
        gdb/gdb.c:32^M
...

Well, it's current master and the tentative patch for PR29867, but I expect
it's unrelated.

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

             reply	other threads:[~2022-12-10  8:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10  8:18 vries at gcc dot gnu.org [this message]
2022-12-10 11:25 ` [Bug gdb/29868] [gdb, s390x] " vries at gcc dot gnu.org
2022-12-12  3:14 ` [Bug tdep/29868] [gdb/tdep, " vries at gcc dot gnu.org
2022-12-12  9:46 ` vries at gcc dot gnu.org
2022-12-12  9:48 ` vries at gcc dot gnu.org
2022-12-12 12:08 ` vries at gcc dot gnu.org
2022-12-12 13:51 ` uweigand at gcc dot gnu.org
2022-12-12 15:08 ` vries at gcc dot gnu.org
2023-01-11  9:26 ` 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-29868-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).