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, 21 Apr 2023 08:00:23 +0000	[thread overview]
Message-ID: <bug-30353-4717-VG1Um7k1St@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 #4 from Tom de Vries <vries at gcc dot gnu.org> ---
In the docs we have:
...
Only set or source commands should be placed into an early initialization file,
and the only set commands that can be used are those that control how GDB
starts up.
...

Hmm, so does "set editing off" "control how GDB starts up"?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-04-21  8:00 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 ` [Bug cli/30353] " vries at gcc dot gnu.org
2023-04-17  9:31 ` 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 [this message]

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-VG1Um7k1St@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).