public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vsfos at foxmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/28018] internal-error: Assertion 'TYPE_LENGTH(index_type) > 0' failed in create_range_type
Date: Wed, 30 Jun 2021 07:17:37 +0000	[thread overview]
Message-ID: <bug-28018-4717-VbUc0u4CNg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28018-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28018

--- Comment #4 from SimonQian <vsfos at foxmail dot com> ---
(In reply to Simon Marchi from comment #1)
> Hi,
> 
> Would you be able to share the program you are debugging, or some other
> reproducer?
> 
> Simon

I prepared a qemu to reproduce the problem, which use mps2 as target device.
The vscode workspace is at:
https://github.com/vsfteam/vsf/tree/master/example/template/project/cmake/mps2


the gdb output log:
Please check OUTPUT tab (Adapter Output) for output from qemu-system-arm
Launching server: "qemu-system-arm" "-cpu" "cortex-m7" "-machine" "mps2-an500"
"-nographic" "-semihosting-config" "enable=on,target=native" "-gdb"
"tcp::50000" "-S" "-kernel"
"Z:\vsf\example\template\project\cmake\mps2\build\vsf_template.elf"
Launching GDB: "arm-none-eabi-gdb.exe" "-q" "--interpreter=mi2"
Reading symbols from
Z:\vsf\example\template\project\cmake\mps2\build\vsf_template.elf...
Reset_Handler () at
Z:/vsf/source/hal/driver/arm/mps2/CMSDK_CM7/startup_ARMCM7.c:191
191     {
Not implemented stop reason (assuming exception): undefined
/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-48_20201124_1606180641/src/gdb/gdb/gdbtypes.c:931:
internal-error: type* create_range_type(type*, type*, const dynamic_prop*,
const dynamic_prop*, LONGEST): Assertion `TYPE_LENGTH (index_type) > 0' 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:
<https://www.gnu.org/software/gdb/bugs/>.

/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-48_20201124_1606180641/src/gdb/gdb/gdbtypes.c:931:
internal-error: type* create_range_type(type*, type*, const dynamic_prop*,
const dynamic_prop*, LONGEST): Assertion `TYPE_LENGTH (index_type) > 0' 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]



And it seems to relate to some compiler options. I will do more test.

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

  parent reply	other threads:[~2021-06-30  7:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 11:00 [Bug breakpoints/28018] New: " vsfos at foxmail dot com
2021-06-27 11:03 ` [Bug breakpoints/28018] " simark at simark dot ca
2021-06-27 11:13 ` vsfos at foxmail dot com
2021-06-27 23:57 ` vsfos at foxmail dot com
2021-06-30  7:17 ` vsfos at foxmail dot com [this message]
2021-06-30  8:14 ` vsfos at foxmail dot com
2021-06-30 11:28 ` vsfos at foxmail dot com
2021-06-30 12:41 ` simark at simark dot ca
2021-10-19  2:01 ` kadler at us dot ibm.com
2021-10-25 18:05 ` kadler at us dot ibm.com
2021-10-28 19:10 ` kadler at us dot ibm.com
2021-10-28 19:41 ` simon.marchi at polymtl dot ca
2021-10-28 21:16 ` kadler at us dot ibm.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-28018-4717-VbUc0u4CNg@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).