public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "r.kloos at campus dot tu-berlin.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27317] New: gdb crashes upon target remote :1234
Date: Tue, 02 Feb 2021 17:26:51 +0000 [thread overview]
Message-ID: <bug-27317-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27317
Bug ID: 27317
Summary: gdb crashes upon target remote :1234
Product: gdb
Version: 9.2
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: r.kloos at campus dot tu-berlin.de
Target Milestone: ---
Created attachment 13196
--> https://sourceware.org/bugzilla/attachment.cgi?id=13196&action=edit
core dump of gdb after described error
The following output is given after trying to use gdb with a symbol file and
trying to execute target remote :1234 :
Reading symbols from kernel_debug...
DW_FORM_strp pointing outside of .debug_str section [in module /<PATH TO FILE
OMITTED>/kernel_debug]
(No debugging symbols found in kernel_debug)
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
../../gdb-9.2/gdb/dwarf2-frame.c:2004: internal-error: const gdb_byte*
decode_frame_entry_1(comp_unit*, const gdb_byte*, int, dwarf2_cie_table&,
dwarf2_fde_table*, eh_frame_type): Assertion `fde->cie != NULL' 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/>.
../../gdb-9.2/gdb/dwarf2-frame.c:2004: internal-error: const gdb_byte*
decode_frame_entry_1(comp_unit*, const gdb_byte*, int, dwarf2_cie_table&,
dwarf2_fde_table*, eh_frame_type): Assertion `fde->cie != NULL' 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)
The symbol file should work, however I don't get why gdb would crash if it
didn't either.
I have included the core dump
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-02-02 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 17:26 r.kloos at campus dot tu-berlin.de [this message]
2021-02-02 17:29 ` [Bug gdb/27317] " r.kloos at campus dot tu-berlin.de
2021-02-02 17:30 ` r.kloos at campus dot tu-berlin.de
2022-03-06 17:41 ` tromey at sourceware dot org
2022-03-06 18:26 ` r.kloos at campus dot tu-berlin.de
2022-03-06 18:30 ` r.kloos at campus dot tu-berlin.de
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-27317-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).