public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jeff at jkent dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/26019] FreeRTOS task breakpoint causes core dump
Date: Thu, 21 May 2020 20:22:47 +0000 [thread overview]
Message-ID: <bug-26019-4717-CSQtDE6Dts@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26019-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26019
--- Comment #3 from Jeff Kent <jeff at jkent dot net> ---
Created attachment 12560
--> https://sourceware.org/bugzilla/attachment.cgi?id=12560&action=edit
Debug log from cortex-debug visual studio code extension
It is an assertion failure. I'll try reproducing this with the gdb console.
/home/jkent/tmp/arm-none-eabi/.build/arm-none-eabi/src/gdb/gdb/frame.c:587:
internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-21 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 3:08 [Bug breakpoints/26019] New: " jeff at jkent dot net
2020-05-21 3:20 ` [Bug breakpoints/26019] " jeff at jkent dot net
2020-05-21 19:00 ` keiths at redhat dot com
2020-05-21 20:22 ` jeff at jkent dot net [this message]
2020-05-21 21:02 ` jeff at jkent dot net
2020-05-21 21:10 ` simark at simark dot ca
2020-05-21 21:23 ` jeff at jkent dot net
2020-05-21 23:09 ` jeff at jkent dot net
2020-05-22 0:02 ` jeff at jkent dot net
2020-05-26 2:34 ` jeff at jkent dot net
2020-06-11 22:46 ` jeff at jkent dot net
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-26019-4717-CSQtDE6Dts@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).