From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BDDC73858C50; Mon, 17 Apr 2023 09:46:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BDDC73858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681724802; bh=QjPrNYA5KTWZeK2caFmTnNxUKikDDyZWlTnlp3AiTw4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=najcM8bbUxx9j5Ra3VFwfn49amV56D1/KKnG1XrRXUCdexFNZcsDb+lzJk/BMrJRM PxbvQQ2/g7jVkZQmquwKGMkpo+bK3rG6Wqua46MvXkq3t2Txkucbzb8gYDRcIRqNhE YGijUf9Lbzh3aVbYPSOOt7F9wcNwkwdLPMz4T4ak= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug cli/30353] [gdb/cli] segfault on -eiex "set editing off" Date: Mon, 17 Apr 2023 09:46:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30353 --- Comment #3 from Tom de Vries --- (In reply to Tom de Vries from comment #2) > The easiest way to fix this is: Alternatively, we could allow it to be set, and deal with it later when interpreters are started. I'm not sure how that would work though. My naive idea is that=20=20 current_ui->command_editing is just set unconditionally, and that interpret= ers deal with that setting accordingly, depending on whether they support it or not. --=20 You are receiving this mail because: You are on the CC list for the bug.=