Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB built with Guile won't start when boot-9 is unavailable.
Date: Sun, 10 Aug 2014 19:12:00 -0000	[thread overview]
Message-ID: <m3ha1k9n33.fsf@sspiff.org> (raw)
In-Reply-To: <83oavsjkjc.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Aug	2014 20:56:23 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sun, 10 Aug 2014 17:27:27 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> 
>> Someone tried to run GDB 7.8 that I built with Guile support without
>> installing Guile first.  (libguile was statically linked into GDB, so
>> no shared library was needed.)  They reported that GDB bailed out with
>> the following error message:
>> 
>>   Throw without catch before boot:
>>   Throw to key misc-error with args ("primitive-load-path" "Unable to find 
>>   file ~S in load path" ("ice-9/boot-9") #f)Aborting.
>> 
>> AFAIR, a snapshot I built about 2 months ago didn't bail out, it just
>> printed a warning that Guile support will be partial.
>> 
>> Is it possible to avoid the fatal error in this case?
>
> Sorry, ignore this: it's because Guile was installed in a directory
> other than the one it was configured for, and GUILE_LOAD_PATH was not
> set.

Ah.

There's still a problem here, as evidenced by requests to have gdb
more tolerant, e.g., of missing Python.
Same reasoning applies to Guile.


  reply	other threads:[~2014-08-10 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 14:27 Eli Zaretskii
2014-08-10 17:56 ` Eli Zaretskii
2014-08-10 19:12   ` Doug Evans [this message]
2014-08-10 19:18     ` Eli Zaretskii

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=m3ha1k9n33.fsf@sspiff.org \
    --to=xdje42@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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