From: Linas Vepstas <linasvepstas@gmail.com>
To: 25267@debbugs.gnu.org
Subject: bug#25267: crashes here only for invalid scheme
Date: Sat, 24 Dec 2016 13:54:04 -0600 [thread overview]
Message-ID: <CAHrUA342YG-C2iknK4GnYo=HJyybvw84oMMRQ6sQMYCdwNJrjA@mail.gmail.com> (raw)
In-Reply-To: <CAHrUA3516D6fHTSJG7hp1pP26wN2DJ_ubbUEUphp56=BqFZHqQ@mail.gmail.com>
FYI: important note: this crashes only because an exception path is
taken. Due to a "bug" in the shell script above, `ctr` is undefined,
so an unbound-variable exception is thrown. When the scheme is valid,
then it does NOT crash here!
--linas
opencog> (NumberNode ctr)
Entering scheme shell; use ^D or a single . on a line by itself to exit.
guile> Backtrace:
In ice-9/boot-9.scm:
157: 12 [catch #t #<catch-closure f83bce0> ...]
In unknown file:
?: 11 [apply-smob/1 #<catch-closure f83bce0>]
In ice-9/boot-9.scm:
157: 10 [catch #t #<catch-closure f83b5c0> ...]
In unknown file:
?: 9 [apply-smob/1 #<catch-closure f83b5c0>]
?: 8 [call-with-input-string "(NumberNode ctr)\n" ...]
In ice-9/boot-9.scm:
2320: 7 [save-module-excursion #<procedure f818930 at
ice-9/eval-string.scm:65:9 ()>]
In ice-9/eval-string.scm:
44: 6 [read-and-eval #<input: string f8049c0> #:lang ...]
37: 5 [lp (NumberNode ctr)]
In ice-9/eval.scm:
387: 4 [eval # ()]
393: 3 [eval #<memoized ctr> ()]
In unknown file:
?: 2 [memoize-variable-access! #<memoized ctr> #<directory
(guile-user) bb3c60>]
In ice-9/boot-9.scm:
102: 1 [#<procedure f181e80 at ice-9/boot-9.scm:97:6 (thrown-k .
args)> unbound-variable ...]
In unknown file:
?: 0 [apply-smob/1 #<catch-closure f83b580> unbound-variable ...]
ERROR: In procedure apply-smob/1:
ERROR: Unbound variable: ctr
ABORT: unbound-variable
next prev parent reply other threads:[~2016-12-24 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 18:43 bug#25267: guile-2.2 crash in GC Linas Vepstas
2016-12-24 19:00 ` Linas Vepstas
2016-12-24 19:54 ` Linas Vepstas [this message]
2017-01-09 21:53 ` Andy Wingo
2017-01-10 6:45 ` Linas Vepstas
2017-03-01 14:43 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHrUA342YG-C2iknK4GnYo=HJyybvw84oMMRQ6sQMYCdwNJrjA@mail.gmail.com' \
--to=linasvepstas@gmail.com \
--cc=25267@debbugs.gnu.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).