unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: a couple bugs related to error reporting and backtraces
Date: Sat, 20 Jun 2009 12:47:02 +0200	[thread overview]
Message-ID: <m3fxdv89nd.fsf@pobox.com> (raw)
In-Reply-To: <87ocspb693.fsf@mithrandir.homeunix.net> (Jose A. Ortega Ruiz's message of "Mon, 15 Jun 2009 22:18:32 +0200")

Heya Jao,

Thanks for the detailed report. I've pushed fixes for both of these
issues.

On Mon 15 Jun 2009 22:18, "Jose A. Ortega Ruiz" <jao@gnu.org> writes:

>   ERROR: In procedure make_objcode_by_mmap:
>   ERROR: Success

>   scheme@(guile-user)> ,i (system base compile)
>   scheme@(guile-user)> (load-compiled (compile-file "/home/jao/tmp/a.scm"))
>
>   Backtrace:
>   In unknown file:
>      ?: 0* [#<vm b7a8a680> #<program b793ed70 at <unknown port>:1:0 ()>]
>      2: 1* [#<program b793ed70 at <unknown port>:1:0 ()>]
>      ?: 2* [load-compiled/vm "/home/jao/.guile-ccache/1.9//home/jao/tmp/a.scm.go"]
>      ?: 3* [ap]
>
>   ERROR: In procedure module-lookup:
>   ERROR: unbound variable: not-bound

Now,

Backtrace:
In unknown file:
   ?: 0* [#<vm b8071650> #<program b7fb7ec0 at <unknown port>:1:0 ()>]
   2: 1* [#<program b7fb7ec0 at <unknown port>:1:0 ()>]
   ?: 2* [load-compiled/vm "/home/wingo/.guile-ccache/1.9//tmp/a.scm.go"]
In /tmp/a.scm:
   4: 3* [ap]

ERROR: In procedure module-lookup:
ERROR: unbound variable: not-bound

I'm not certain why the load-compiled call does not have source info,
though. It seems the "2" on frame 1 corresponds to the second line of
stdin; perhaps that source info is getting misplaced. Let us know if you
find other bugs.

Andy
-- 
http://wingolog.org/




      reply	other threads:[~2009-06-20 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 20:18 a couple bugs related to error reporting and backtraces Jose A. Ortega Ruiz
2009-06-20 10:47 ` Andy Wingo [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

  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=m3fxdv89nd.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=jao@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).