[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: core dump.
From: |
Kevin Ryde |
Subject: |
Re: core dump. |
Date: |
Thu, 22 Jan 2004 07:49:02 +1000 |
User-agent: |
Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) |
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).
- core dump., Han-Wen Nienhuys, 2004/01/20
- Re: core dump.,
Kevin Ryde <=