Re: core dump.

[Kevin Ryde]

Han-Wen Nienhuys  <address@hidden> writes:
>
> elapsed time: 0.01 secondsBacktrace:
> In c.ly:
>    2: 0* [determine-split-list #(# # # # ...) #(# # # #)]
> In unknown file:
>    ?: 1  
> Program received signal SIGSEGV, Segmentation fault.
> [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).