From: Mike Mater <mmater@biovigil.com>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: Bug
Date: Thu, 3 Feb 2022 20:02:05 +0000 [thread overview]
Message-ID: <CH2PR22MB18306416EA2E9A0DEF2C910FAE289@CH2PR22MB1830.namprd22.prod.outlook.com> (raw)
Not sure what to do. I am getting a error with my debugger as part of VSC. It pointed me to here to report it. I do not have an account.
Resetting target
[New Remote target]
/mnt/workspace/workspace/GCC-9-pipeline/jenkins-GCC-9-pipeline-100_20191030_1572397542/src/gdb/gdb/infrun.c:5338: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session?
(y or n) [answered Y; input not from terminal]
This is a bug, please report it.
For instructions, see: http://www.gnu.org/software/gdb/bugs/.
/mnt/workspace/workspace/GCC-9-pipeline/jenkins-GCC-9-pipeline-100_20191030_1572397542/src/gdb/gdb/infrun.c:5338: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB?
(y or n) [answered Y; input not from terminal]
Contact me if you want more information. This has happened on twice. The first time reinstalling VSC, Nordic command line tools, etc appeared to work. I am not sure what to do. This is very flustrating.
Michael Mater
Engineering
m: 734-255-2079
e: mmater@biovigil.com<mailto:mmater@biovigil.com>
w: biovigil.com<http://biovigilsystems.com/>
B I O V I G I L
Hand Hygiene Solutions
reply other threads:[~2022-02-03 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CH2PR22MB18306416EA2E9A0DEF2C910FAE289@CH2PR22MB1830.namprd22.prod.outlook.com \
--to=mmater@biovigil.com \
--cc=overseers@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).