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/26881] infrun.c:6384: internal-error: void process_event_stop_test(execution_control_state*): Assertion `ecs->event_thread->control.exception_resume_breakpoint != NULL' failed.
Date: Sat, 14 Nov 2020 19:45:04 +0000 [thread overview]
Message-ID: <bug-26881-4717-6r5danWeex@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26881-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26881
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> Hmm, it seems this reproduces in the test-suite:
> ...
> (gdb) PASS: gdb.cp/nextoverthrow.exp: post-check - next over a throw 3
> next^M
> /home/vries/gdb_versions/devel/src/gdb/infrun.c:6384: internal-error: void
> process_event_stop_test(execution_control_state*): Assertion
> `ecs->event_thread->control.exception_resume_breakpoint != NULL' 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.cp/nextoverthrow.exp: next
> past catch (GDB internal error)
> ...
I also managed to reproduce this at gdb-8.3-branch branchpoint.
I haven't seen this failure before, but it's caused by the backport for gcc
PR97774 - "Incorrect line info for try/catch" (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97774 ) landing on the compiler
I'm using.
So, this should be reproducible for anyone using gcc-10 or later.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-14 19:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 9:58 [Bug gdb/26881] New: " vries at gcc dot gnu.org
2020-11-14 10:41 ` [Bug gdb/26881] " vries at gcc dot gnu.org
2020-11-14 10:45 ` vries at gcc dot gnu.org
2020-11-14 10:49 ` vries at gcc dot gnu.org
2020-11-14 13:07 ` vries at gcc dot gnu.org
2020-11-14 19:45 ` vries at gcc dot gnu.org [this message]
2020-11-15 0:24 ` vries at gcc dot gnu.org
2020-11-15 0:30 ` vries at gcc dot gnu.org
2020-11-16 14:35 ` vries at gcc dot gnu.org
2020-11-21 8:58 ` vries at gcc dot gnu.org
2021-01-05 10:41 ` vries at gcc dot gnu.org
2021-01-05 10:44 ` vries at gcc dot gnu.org
2021-01-05 13:30 ` [Bug breakpoints/26881] " vries at gcc dot gnu.org
2021-01-08 10:11 ` cvs-commit at gcc dot gnu.org
2021-01-08 10:58 ` cvs-commit at gcc dot gnu.org
2021-01-08 11:00 ` vries at gcc dot gnu.org
2021-06-27 17:49 ` ahmedsayeed1982 at yahoo dot com
2021-08-10 11:45 ` ucelsanicin at yahoo dot com
2021-08-27 17:51 ` ribevi6798 at enamelme dot com
2021-08-28 18:31 ` buranlevent at yahoo dot com
2021-09-06 9:10 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:40 ` mehmetgelisin at aol dot com
2021-09-14 17:28 ` johnb6174 at gmail dot com
2021-09-14 18:48 ` mark at klomp dot org
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-17 19:48 ` vmireskazki at gmail dot com
2021-10-18 19:58 ` ahmedsayeed1982 at hotmail dot com
2021-10-19 7:15 ` progonsaytu at gmail dot com
2021-10-23 13:45 ` fiteva5725 at bomoads dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-10-29 10:57 ` kimolsun2020 at outlook dot com
2021-10-29 12:06 ` huracantili20 at gmail dot com
2021-11-02 15:21 ` gepaw63633 at dukeoo dot com
2021-11-06 21:11 ` paneki8601 at dukeoo dot com
2021-11-13 19:31 ` tesaso8237 at funboxcn dot com
2021-11-16 19:04 ` xecana8007 at funboxcn dot com
2021-11-22 7:37 ` gexed96894 at keagenan 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-26881-4717-6r5danWeex@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).