public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
* [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 @ 2020-11-12 23:44 vries at gcc dot gnu.org 2020-12-10 10:31 ` [Bug breakpoints/26873] " vries at gcc dot gnu.org ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: vries at gcc dot gnu.org @ 2020-11-12 23:44 UTC (permalink / raw) To: gdb-prs 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. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [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 2020-11-12 23:44 [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 vries at gcc dot gnu.org @ 2020-12-10 10:31 ` 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 2 siblings, 0 replies; 4+ messages in thread From: vries at gcc dot gnu.org @ 2020-12-10 10:31 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=26873 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Hit once more, on powerpc64-suse-linux-gnu -m32/-fpie/-FPIE. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [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 2020-11-12 23:44 [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 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 2022-09-28 12:34 ` vries at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: vries at gcc dot gnu.org @ 2022-09-28 12:14 UTC (permalink / raw) To: gdb-prs 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. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [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 2020-11-12 23:44 [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 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 @ 2022-09-28 12:34 ` vries at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: vries at gcc dot gnu.org @ 2022-09-28 12:34 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=26873 --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Tom de Vries from comment #2) > The test-case expects two hardware watchpoints, but gets one hardware and > one software watchpoint. So, it's possible that having both hardware and software watch points at the same time is what is required to reproduce this. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-09-28 12:34 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-11-12 23:44 [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 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 2022-09-28 12:34 ` vries at gcc dot gnu.org
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).