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 21:02:47 +0000	[thread overview]
Message-ID: <bug-26019-4717-OzzfoxCB1a@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 #4 from Jeff Kent <jeff at jkent dot net> ---
I was able to repro this bug with the following gdb session.  I'm using 8.3.0
because I accidentally wiped out my toolchain with GDB 9.1.  Woops.  It's
currently rebuilding.

GNU gdb (GNU Tools for Arm Embedded Processors 9-2019-q4-major)
8.3.0.20190709-git
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-linux-gnu --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) file examples/freertos-demo/build/freertos-demo.elf
Reading symbols from examples/freertos-demo/build/freertos-demo.elf...
(gdb) target remote localhost:2331
Remote debugging using localhost:2331
_vect_irq () at ../../baremetal/entry.S:41
41              ldr pc, [pc, #24]
(gdb) monitor halt
(gdb) monitor reset
Resetting target
(gdb) load
Loading section .entry, size 0xa4 lma 0x0
Loading section .entry_thumb, size 0x24 lma 0xa4
Loading section .text, size 0x3aa8 lma 0xc8
Loading section .rodata, size 0x58 lma 0x3b70
Loading section .data, size 0x10 lma 0x3bc8
Start address 0x0, load size 15320
Transfer rate: 56 KB/sec, 3064 bytes/write.
(gdb) monitor reset
Resetting target
(gdb) break examples/freertos-demo/main.c:61
Breakpoint 1 at 0x3b64: file main.c, line 61.
(gdb) continue
Continuing.

Breakpoint 1, task_b (
/mnt/workspace/workspace/GCC-9-pipeline/jenkins-GCC-9-pipeline-100_20191030_1572397542/src/gdb/gdb/frame.c:558:
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.
Quit this debugging session? (y or n) y

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/frame.c:558:
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.
Create a core file of GDB? (y or n) y
Aborted (core dumped)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-05-21 21:02 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
2020-05-21 21:02 ` jeff at jkent dot net [this message]
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-OzzfoxCB1a@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).