On Thu, Feb 27, 2020 at 10:41:32PM +0100, Kurt Pagani wrote:
>
> The second issue concerns big files (compile or read doesn't matter):
>
>
> --ECL
> -- (1) -> )r bigfile
> --
> -- >> System error:
> -- C-STACK overflow at size 1042432. Stack can probably be resized.
> -- Proceed with caution.
>
> --SBCL
> -- >> System error:
> -- Control stack exhausted (no more space for function call frames).
> -- This is probably due to heavily nested or infinitely recursive function
> -- calls, or a tail call that SBCL cannot or has not optimized away.
> --
> -- PROCEED WITH CAUTION.
>
> Example:
> - http://fricas-wiki.math.uni.wroc.pl/AWAIC
That one looks like sbcl bug: stack overflow is during lisp compilation.
> - attached bigfile.input (mostly comments, ~30k lines)
>
> I'm wondering why reading a file uses recursion?
Recursion in general is reasonable. Our scanned uses too complicated
method which usually keeps recursion depth low. But on long
streches of comments the method backfires and recursion depth
is very high. Adding some actual code (so distnce between executable
lines is at most 5000) between comment makes problem go away,
so it there is at least partial workaround. Anyway, I was
thinking about simplifyng scanner, but up to now "do not fix
what is not broken" won. Now I will have good excuse
to work on it. To say the truth I am more worried about
releated problem: skiping long parts using ')if' and ')endif'
also leads to crash...
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/20200228165849.GB17944%40math.uni.wroc.pl.
