[EMAIL PROTECTED] writes:
> > [Switching to Thread 1074493760 (LWP 27557)]
> > 0x4002f524 in unmemocar (form=0x4050d7b8, env=0x167f) at eval.c:2246
> > (gdb) bt
> > #0 0x4002f524 in unmemocar (form=0x4050d7b8, env=0x167f) at eval.c:2246
> > #1 0x4002f654 in scm_unmemocopy (x=0x404da7e8, env=0x4050de58) at eval.c:2469
>
> I've seen something like this when an error (an ordinary scheme level
> error) occurs in code generated by a procedure->macro. Dunno if
> that's what's happening here. Running without --debug normally avoids
> the segv (though obviously one can't tell quite where it went wrong).
Yeah, I found out so far. Now I have to figure out what in my 10000
lines of Scheme code is causing
ERROR: In procedure car:
ERROR: Wrong type argument in position 1: ()
Does anyone actually know how the evaluator works?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
_______________________________________________
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile
