Re: Bug: Unbound variable:

[Neil Jerram]

2008/12/14 Linas Vepstas <address@hidden>:
> 2008/12/13 Ludovic Courtès <address@hidden>:
>>
>> Are you able to get a meaningful backtrace when that exception is
>> raised?
>
> Sure .. but its in my code .. for example:
>
> guile> (doit)
> Backtrace:
> In current input:
>   1:  0* [doit]
>   1:  1  [process-data
> "/home2/linas/src/novamente/data/enwiki/enwiki-20080524/parsed/A" ...]
>    ...
>  24:  2  [for-each #<procedure process-file #> #]
>   ?:  3* [process-file "Andrew Van de Kamp.xml"]
>   3:  4* (let ((fullname #) (donename #)) (system (string-join #)) ...)
>  14:  5* [ldj-process]
>   2:  6  [for-each #<procedure ldj-process-document (doco)> (#)]
>   ?:  7* [ldj-process-document #]
>   2:  8* [for-each #<procedure ldj-process-sentence (sent-node)> ...
>   2:  9*  [document-get-sentences #]
>   2: 10   (cog-get-reference doco)
>
> <unnamed port>:2:9: In expression (cog-get-reference doco):
> <unnamed port>:2:9: Unbound variable: cog-get-reference
> ABORT: unbound-variable
> guile>

Could you get a C backtrace too, by setting a breakpoint on
error_unbound_variable?  There are two places that call
error_unbound_variables, and at first glance the one from eval.c line
2884 looks more unusual, so it would be interesting to know if it was
that place causing your problem.

Regards,
     Neil