public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/18140] New: duplicate DW_TAG_label's in dwarf cause ICE
Date: Wed, 18 Mar 2015 18:14:00 -0000 [thread overview]
Message-ID: <bug-18140-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18140
Bug ID: 18140
Summary: duplicate DW_TAG_label's in dwarf cause ICE
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: aldyh at redhat dot com
This is incorrect dwarf that I mistakenly generated in GCC's debug-early
project. I am generating two DW_TAG_label's for the same source label, and of
of them doesn't have line information.
reynosa:/build/dearly/gcc$ cat a.c
int
main ()
{
here:
return 0;
}
Faulty dwarf is:
<2><4e>: Abbrev Number: 3 (DW_TAG_label)
<4f> DW_AT_name : (indirect string, offset: 0x0): here
<53> DW_AT_decl_file : 1
<54> DW_AT_decl_line : 4
<2><55>: Abbrev Number: 4 (DW_TAG_label)
<56> DW_AT_name : (indirect string, offset: 0x0): here
<5a> DW_AT_decl_file : 1
<5b> DW_AT_decl_line : 4
<5c> DW_AT_low_pc : 0x4004ca
End result:
(gdb) b main
Breakpoint 1 at 0x4004ca: file a.c, line 5.
(gdb) r
Starting program: /home/build/dearly/gcc/a.out
Breakpoint 1, main () at a.c:5
5 return 0;
(gdb) b here
/source/binutils-gdb/gdb/linespec.c:2459: internal-error: decode_line_full:
Assertion `result.nelts == 1 || canonical->pre_expanded' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-03-18 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 18:14 aldyh at redhat dot com [this message]
2020-08-27 11:54 ` [Bug breakpoints/18140] " 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-18140-4717@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).