public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/29223] gdb crashes with empty guile command in configuration file
Date: Sat, 04 Jun 2022 16:06:32 +0000	[thread overview]
Message-ID: <bug-29223-4717-D7R7MM54GR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29223-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29223

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-06-04
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Nikolaos Chatzikonstantinou from comment #2)

> Is the `add-auto-load-safe-path` used correctly? Doesn't seem to load
> anything
> for me. E.g. if the file only contains `set startup-quietly on`, the splash
> still shows.

I think 'startup-quietly' takes effect too late in this case.

> 
> The way I obtain the crash is by
> 
>     echo guile > ~/.config/gdb/gdbearlyinit

I can reproduce it this way, thank you.

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

      parent reply	other threads:[~2022-06-04 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 10:54 [Bug cli/29223] New: " nchatz314 at gmail dot com
2022-06-03 17:20 ` [Bug cli/29223] " tromey at sourceware dot org
2022-06-04  1:17 ` nchatz314 at gmail dot com
2022-06-04  5:43 ` nchatz314 at gmail dot com
2022-06-04 10:26 ` nchatz314 at gmail dot com
2022-06-04 16:06 ` tromey at sourceware dot 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-29223-4717-D7R7MM54GR@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).