Re: a couple bugs related to error reporting and backtraces

[Andy Wingo]

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" <address@hidden> 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/