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/30353] [gdb/cli] segfault on -eiex "set editing off"
Date: Fri, 14 Apr 2023 10:09:02 +0000 [thread overview]
Message-ID: <bug-30353-4717-7ZW3mv201y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30353-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30353
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Segfault happens because we dereference nullptr interp:
...
Thread 1 "gdb" received signal SIGSEGV, Segmentation fault.
0x0000000000893970 in interp_supports_command_editing (interp=0x0) at
/data/vries/gdb/src/gdb/interps.c:330
330 return interp->supports_command_editing ();
...
Called from here:
...
(gdb) up
#1 0x0000000000787112 in change_line_handler (editing=0) at
/data/vries/gdb/src/gdb/event-top.c:292
292 if (!interp_supports_command_editing (top_level_interpreter ())
....
Called from here:
...
(gdb) up
#2 0x0000000000c5554c in set_editing (args=0x0, from_tty=1, c=0x2ab07a0)
at /data/vries/gdb/src/gdb/top.c:2141
2141 change_line_handler (set_editing_cmd_var);
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-14 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 10:06 [Bug cli/30353] New: " vries at gcc dot gnu.org
2023-04-14 10:09 ` vries at gcc dot gnu.org [this message]
2023-04-17 9:31 ` [Bug cli/30353] " vries at gcc dot gnu.org
2023-04-17 9:46 ` vries at gcc dot gnu.org
2023-04-21 8:00 ` 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-30353-4717-7ZW3mv201y@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).