-
Notifications
You must be signed in to change notification settings - Fork 1
fix(bin): run interpreter on a large-stack thread to avoid deep-nesting overflow 🌀 #176
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
Open
timfennis
wants to merge
1
commit into
master
Choose a base branch
from
bugfix/parser-recursion-depth-limit
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| //! Regression test: deeply nested input must not crash the interpreter. | ||
| //! | ||
| //! Each nesting level costs a native stack frame in the parser and in every | ||
| //! later phase that walks the AST. On the default main-thread stack this used | ||
| //! to overflow and abort the process (SIGABRT) at a few hundred levels. `ndc` | ||
| //! now runs the interpreter on a worker thread with a large explicit stack, so | ||
| //! input far deeper than that evaluates normally. See | ||
| //! <https://github.com/timfennis/andy-cpp/issues/175>. | ||
|
|
||
| // This integration test links `ndc_bin`'s dependencies but drives the built | ||
| // binary instead of calling them, so silence `unused-crate-dependencies`. | ||
| #![allow(unused_crate_dependencies)] | ||
|
|
||
| use std::fs; | ||
| use std::process::Command; | ||
|
|
||
| #[test] | ||
| fn deeply_nested_input_does_not_overflow_the_stack() { | ||
| // Deep enough to overflow the default main-thread stack (which gave up | ||
| // around a few hundred levels), shallow enough to fit the worker thread's | ||
| // large stack with room to spare. | ||
| let depth = 2000; | ||
| let source = format!("print({}1{})", "(".repeat(depth), ")".repeat(depth)); | ||
|
|
||
| let path = std::env::temp_dir().join(format!("ndc_deep_nesting_{}.ndc", std::process::id())); | ||
| fs::write(&path, &source).expect("write temp script"); | ||
|
|
||
| let output = Command::new(env!("CARGO_BIN_EXE_ndc")) | ||
| .arg(&path) | ||
| .output() | ||
| .expect("run ndc"); | ||
|
|
||
| let _ = fs::remove_file(&path); | ||
|
|
||
| assert!( | ||
| output.status.success(), | ||
| "ndc crashed on {depth}-deep nesting (status {:?}); a stack overflow would show up here.\nstderr:\n{}", | ||
| output.status, | ||
| String::from_utf8_lossy(&output.stderr), | ||
| ); | ||
| assert_eq!( | ||
| String::from_utf8_lossy(&output.stdout).trim(), | ||
| "1", | ||
| "the nested expression should evaluate to 1", | ||
| ); | ||
| } |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For source nested beyond what this fixed 512 MiB stack can hold, this still reaches the same recursive parser/analyser/compiler walks and aborts the process; in the inspected diff
ndc_parseris unchanged, so this line only raises the crash threshold rather than turning crafted deep input into a normal error. A file likeprint(+ many more nested parentheses than the worker stack can handle +1will still terminate with a stack overflow, so the CLI remains vulnerable unless the parser enforces a depth limit before later phases walk the AST.Useful? React with 👍 / 👎.