unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Noah Lavine <noah.b.lavine@gmail.com>, guile-devel@gnu.org
Subject: Re: An Error in Early Boot
Date: Thu, 14 Oct 2010 16:36:24 -0700 (PDT)	[thread overview]
Message-ID: <814573.44378.qm@web37903.mail.mud.yahoo.com> (raw)
In-Reply-To: <AANLkTi=o7f_YAKNFHMAs9Xr8taGt+9nwMkUTJbxZamQp@mail.gmail.com>

> From: Noah Lavine <noah.b.lavine@gmail.com>
> 
> Hello,
> 
> I got into a situation just now when Guile was generating an error
> very early in the boot process (it was loading some objcode from
> scm_init_eval_in_scheme(), I think, although I haven't looked enough
> to be sure). The fun part is, instead of printing an error message, it
> got into an infinite recursion that eventually ended in a memory
> fault.
> 
> The reason is that scm_error_scm in error.c calls scm_ithrow (error.c:315),
> which finds its way through scm_throw and some VM calls to
> pre_init_throw (throw.c:495)
> which in turn gets it to scm_at_abort, which goes to scm_c_abort,
> which finally calls scm_misc_error (control.c:210) because it can't
> find a prompt on the dynamic stack because the error is too early,
> which leads back to scm_error_scm again.

Hi Noah,

FWIW, I also noticed the infinite recusion problem in bug #30162.

http://savannah.gnu.org/bugs/?30162

At the time, I thought that the following revision might be the one
that caused the problem.

http://git.savannah.gnu.org/cgit/guile.git/commit/?id=c6a32a2cd59190dcf17c7fb3022588f56079a03e


-Mike



  reply	other threads:[~2010-10-14 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 21:06 An Error in Early Boot Noah Lavine
2010-10-14 23:36 ` Mike Gran [this message]
2010-10-15  2:31   ` Noah Lavine

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=814573.44378.qm@web37903.mail.mud.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=guile-devel@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    /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).