-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on Test Input #1
Comments
Debugging this in dlv is proving challenging -- I prefer gdb, among other things. |
It's possible I've overlooked an important warning in the generated code, as I've generally paid little attention to those except when trying to track down a transpile or build error. So I'll focus on that next, reviewing the warnings in the .go code. |
Have been trying to remove more Having completed the performance analysis needed, this is now Deferred as a "nice to have" here, and I'll move on to the next task. |
The problem went away during iterative hand-conversion of the code to native Go facilities as of this commit: It's big mainly because of removal of c2go-generated I suspect the |
The problem has since returned, but only when profiling is enabled (using either profiler currently supported). I made a variety of changes, including converting list_read() to an iterative algorithm (to avoid running out of stack reading large inputs), but restoring the recursive algorithm doesn't avoid the crashes, so that isn't likely to be the problem. Still feels like a GC problem to me -- and since I do want to understand some weird performance behavior I'm seeing (in particular, generating output, by not specifying the |
One of the more-amusing errors that came out (only once though) was:
For posterity, here's the complete output:
|
When reading Z.lisp, a cut-down version of zero-test.lisp, lisp-zero-go crashes in ways that seem to vary by invocation or at least by re-build.
E.g.:
The text was updated successfully, but these errors were encountered: