-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Stack overflow when running cargo doc #40936
Labels
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
Comments
GuillaumeGomez
added
the
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
label
Mar 31, 2017
I'd like to work on this issue. |
@Aaron1011: Sure, go ahead. |
Aaron1011
added a commit
to Aaron1011/rust
that referenced
this issue
Apr 9, 2017
Previously, rustdoc's LibEmbargoVisitor unconditionally visited the child modules of an external crate. If a module re-exported its parent via 'pub use super::*', rustdoc would re-walk the parent, leading to infinite recursion. This commit makes LibEmbargoVisitor store already visited modules in an FxHashSet, ensuring that each module is only walked once. Fixes rust-lang#40936
frewsxcv
added a commit
to frewsxcv/rust
that referenced
this issue
Apr 14, 2017
Fix rustdoc infinitely recursing when an external crate reexports itself Previously, rustdoc's LibEmbargoVisitor unconditionally visited the child modules of an external crate. If a module re-exported its parent via `pub use super::*`, rustdoc would re-walk the parent, leading to infinite recursion. This commit makes LibEmbargoVisitor store already visited modules in an FxHashSet, ensuring that each module is only walked once. Fixes rust-lang#40936
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running
cargo doc
crashes withSteps to reproduce:
The last working ref is das-labor/panopticon@c460ecd
Meta
rustc --version --verbose
:Backtrace: N/A
A
ulimit -s unlimited
does not help. I tried with nightly but that crashes with an (unrelated?) error.The text was updated successfully, but these errors were encountered: