Skip to content
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

Fix interpreter segfaults #1112

Open
fare opened this issue Jan 23, 2024 · 0 comments
Open

Fix interpreter segfaults #1112

fare opened this issue Jan 23, 2024 · 0 comments

Comments

@fare
Copy link
Collaborator

fare commented Jan 23, 2024

Interpreter tends to segfault when too many modules are imported (due to memory corruption? stack overflow?)

Example file attached (gzip'ed to pass the GitHub filter): i.scm.gz

Uncomment the top import and it works (loops forever solving the day 14 problem). Comment it and segfault happens early on (usually during the first attempt). Try to import fewer / smaller modules (including transitive dependencies) and the segfaults will happen less often (more iterations needed to trigger it) but eventually may still.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant