public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/30362] New: [gdb/cli] segfault on gdb -eiex "show <something>"
Date: Mon, 17 Apr 2023 09:35:09 +0000 [thread overview]
Message-ID: <bug-30362-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30362
Bug ID: 30362
Summary: [gdb/cli] segfault on gdb -eiex "show <something>"
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
...
$ gdb -eiex "show data-directory"
Fatal signal: Segmentation fault
----- Backtrace -----
0x596558 gdb_internal_backtrace_1
/data/vries/gdb/src/gdb/bt-utils.c:122
0x5965fb _Z22gdb_internal_backtracev
/data/vries/gdb/src/gdb/bt-utils.c:168
0x788116 handle_fatal_signal
/data/vries/gdb/src/gdb/event-top.c:962
0x788282 handle_sigsegv
/data/vries/gdb/src/gdb/event-top.c:1035
0x7fbccac758bf ???
0xca1c28 _ZNK6ui_out12is_mi_like_pEv
/data/vries/gdb/src/gdb/ui-out.c:812
0x60ccfe _Z15do_show_commandPKciP16cmd_list_element
/data/vries/gdb/src/gdb/cli/cli-setshow.c:671
0xc527d9 _Z15execute_commandPKci
/data/vries/gdb/src/gdb/top.c:681
0x90c88f catch_command_errors
/data/vries/gdb/src/gdb/main.c:517
0x90ca9b execute_cmdargs
/data/vries/gdb/src/gdb/main.c:616
0x90d3bb captured_main_1
/data/vries/gdb/src/gdb/main.c:1042
0x90df99 captured_main
/data/vries/gdb/src/gdb/main.c:1308
0x90e038 _Z8gdb_mainP18captured_main_args
/data/vries/gdb/src/gdb/main.c:1337
0x41a9bd main
/data/vries/gdb/src/gdb/gdb.c:32
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-04-17 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 9:35 vries at gcc dot gnu.org [this message]
2023-04-21 7:59 ` [Bug cli/30362] " 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-30362-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).