[Ecls-list] Flaw in subtypep ? / catching stack-overflow ? / memory-limits experience ?

Matthew Mondor mm_lists at pulsar-zone.net
Mon Oct 28 23:41:24 UTC 2013

On Mon, 28 Oct 2013 19:38:46 +0100
Eckhard Wiederhold <ecky at ecky.fr> wrote:

>     - (subtypep 'si:property-list 'condition) and (subtypep 
> 'si::proper-list 'condition) raise "Stack overflow."
>       serious-condition
>     Question: Is this some issue I need to report here: 
> http://sourceforge.net/p/ecls/bugs/ ? Or is it normal
>     behaviour ?

the existing http://sourceforge.net/p/ecls/bugs/141/ might be related

>     Top level in: #<process TOP-LEVEL>.
>     Any attempt to catch it later failed and i ended up on toplevel ... 
> this seems odd to me but it matches
>     in a strange way the fact that you may, if a stack-overflow occurs, 
> resize the stack two times, after that
>     you're put to toplevel automatically. Is there any way to get around 
> this?

That might be worth reporting as another bug.  Interestingly, I've also
encountered lately a case where SIGSEGV/SIGBUS might be handlable or
not, inconsistently, and when it cannot be handled the REPL jumps to
the TOP-LEVEL at which point SLIME disconnects (but it can reconnect
without restarting ECL in my case).  This was observed when fiddling
around to report http://sourceforge.net/p/ecls/bugs/272/


More information about the ecl-devel mailing list