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/26284] [arm] infrun.c:5312: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed Date: Wed, 19 Aug 2020 08:19:49 +0000 [thread overview] Message-ID: <bug-26284-4717-8i2Jgq9eGQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26284-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26284 --- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> --- This may be a duplicate of a couple of PRs: - PR21497 "FreeBSD: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed" - PR21774 "Ubuntu: infrun.c:5565: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed" - PR22063 "infrun.c:5570: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. - PR22925 "gdb assumes target can activate threads at will, causes internal error in infrun.c in 'finish_step_over'" Interesting about this occurrence is: - it reproduced with a testsuite test-case. - the test-case is not a pthreads test-case, which hopefully may make things easier. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-19 8:19 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-22 15:15 [Bug gdb/26284] New: " vries at gcc dot gnu.org 2020-07-22 15:15 ` [Bug gdb/26284] " vries at gcc dot gnu.org 2020-07-22 15:24 ` vries at gcc dot gnu.org 2020-08-10 13:57 ` vries at gcc dot gnu.org 2020-08-19 8:15 ` vries at gcc dot gnu.org 2020-08-19 8:17 ` vries at gcc dot gnu.org 2020-08-19 8:19 ` vries at gcc dot gnu.org [this message] 2020-09-15 10:57 ` vries at gcc dot gnu.org 2020-09-15 11:04 ` luis.machado at linaro dot org 2021-09-09 11:49 ` [Bug gdb/26284] " vries at gcc dot gnu.org 2022-11-29 20:54 ` tromey at sourceware dot org 2023-01-19 10:35 ` vries at gcc dot gnu.org 2023-10-01 3:42 ` [Bug gdb/26284] gdb.base/step-over-syscall.exp: " simark at simark dot ca 2023-10-01 3:43 ` simark at simark dot ca 2023-11-28 9:24 ` 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-26284-4717-8i2Jgq9eGQ@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: linkBe 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).