public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/17174] New: infrun.c:4400: internal-error: process_event_stop_test: Assertion `ecs->event_thread->control.exception_resume_breakpoint != NULL' failed.
Date: Fri, 18 Jul 2014 11:09:00 -0000 [thread overview]
Message-ID: <bug-17174-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17174
Bug ID: 17174
Summary: infrun.c:4400: internal-error:
process_event_stop_test: Assertion
`ecs->event_thread->control.exception_resume_breakpoin
t != NULL' failed.
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: jan.kratochvil at redhat dot com
Host: x86_64-linux-gnu
Target: x86_64-linux-gnu
i=0;while runtest gdb.threads/multiple-step-overs.exp;do i=$[$i+1];echo
------------------------------$i;done
infrun: BPSTAT_WHAT_CLEAR_LONGJMP_RESUME
infrun.c:4400: internal-error: process_event_stop_test: Assertion
`ecs->event_thread->control.exception_resume_breakpoint != NULL' failed.
At about 1st to 4th run.
It happens already on the first check-in of this testcase:
99619beac6252113fed212fdb9e1ab97bface423
It still happens on current FSF GDB trunk:
fe1873d01904620c71a309249c0ae029e53ae0b6
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-07-18 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 11:09 jan.kratochvil at redhat dot com [this message]
2014-07-18 11:19 ` [Bug breakpoints/17174] " jan.kratochvil at redhat dot com
2015-01-08 20:52 ` jan.kratochvil at redhat dot com
2015-01-08 20:54 ` jan.kratochvil at redhat dot com
2020-11-09 12:12 ` szotsaki at gmail dot com
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-17174-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).