public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nchatz314 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/29223] New: gdb crashes with empty guile command in configuration file
Date: Thu, 02 Jun 2022 10:54:55 +0000 [thread overview]
Message-ID: <bug-29223-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29223
Bug ID: 29223
Summary: gdb crashes with empty guile command in configuration
file
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: nchatz314 at gmail dot com
Target Milestone: ---
If I create a configuration file with contents
guile
and run gdb, it crashes. I'm trying to debug this to submit a patch, but in the
meantime I would like to at least submit this bug report, as gdb itself
instructs me to do so:
Fatal signal: Segmentation fault
----- Backtrace -----
0x55baf3e21e3f ???
0x55baf3f35928 ???
0x55baf3f35ae6 ???
0x7f2915ebda6f ???
0x55baf42282c4 ???
0x55baf3e69d3d ???
0x55baf3f76439 ???
0x55baf3e59074 ???
0x55baf41f25b7 ???
0x55baf3f35dac ???
0x55baf41efcfe ???
0x55baf3e68dce ???
0x55baf3e57f2a ???
0x55baf400e5b1 ???
0x55baf4010c2c ???
0x55baf401113e ???
0x55baf3d4fe6d ???
0x7f2915ea854f ???
0x7f2915ea8608 ???
0x55baf3d58744 ???
0xffffffffffffffff ???
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-02 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 10:54 nchatz314 at gmail dot com [this message]
2022-06-03 17:20 ` [Bug cli/29223] " tromey at sourceware dot org
2022-06-04 1:17 ` nchatz314 at gmail dot com
2022-06-04 5:43 ` nchatz314 at gmail dot com
2022-06-04 10:26 ` nchatz314 at gmail dot com
2022-06-04 16:06 ` tromey at sourceware dot 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-29223-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).