public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "henri.inndorf at tutanota dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29754] New: gdb immediately segfaults on startup
Date: Sun, 06 Nov 2022 17:35:44 +0000 [thread overview]
Message-ID: <bug-29754-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29754
Bug ID: 29754
Summary: gdb immediately segfaults on startup
Product: gdb
Version: 12.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: henri.inndorf at tutanota dot com
Target Milestone: ---
Upon running GDB (with and without specifying a file), it immediately crashes
with the following messages:
Fatal signal: Segmentation fault
----- Backtrace -----
0x56114648eb6b ???
0x561146582fa8 ???
0x561146583198 ???
0x7f77607e29ff ???
0x7f7760900ffd ???
0x7f77614d0cbb ???
0x7f77614d0db6 ???
0x7f77614be25a ???
0x5611467b8474 ???
0x56114661a5aa ???
0x5611468f54cc ???
0x5611463fabff ???
0x7f77607cd28f ???
0x7f77607cd349 ???
0x5611464011e4 ???
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/>.
[1] 2880 segmentation fault (core dumped) gdb
My machine is running Linux 4.19.262-1-MANJARO x86_64.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-06 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 17:35 henri.inndorf at tutanota dot com [this message]
2022-11-07 14:03 ` [Bug gdb/29754] " tromey at sourceware dot org
2022-11-07 22:19 ` henri.inndorf at tutanota dot 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-29754-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).