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.

Sign up for GitHub

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

Jump to bottom

rustc stack exhaustion with RUST_LOG=rustc #6261

Closed
thomaslee opened this issue May 6, 2013 · 3 comments
Closed

rustc stack exhaustion with RUST_LOG=rustc #6261

thomaslee opened this issue May 6, 2013 · 3 comments

Comments

@thomaslee
Copy link
Contributor

Reproducable vs. the incoming branch using the following source file:

https://gist.github.com/thomaslee/5522568#file-foo-rs

Exact invocation:

RUST_LOG=rustc rustc --out-dir . foo.rs

Dies with:

rust: task 12dc140 ran out of stack

Had a bit of trouble getting a copy of the resulting gdb backtrace because of some technical issues with my desktop, but seems to be easily reproducible. I'll try to get that stack trace in the next day or so if nobody beats me to it.
@thomaslee
Copy link
Contributor Author

May also be worth noting that I encountered this while digging into issue 4202. I don't think they're related, but I'm not familiar enough with the code base to be certain.

@sanxiyn
Copy link
Member

sanxiyn commented May 6, 2013

Same as #5958?

@Aatch
Copy link
Contributor

Aatch commented Jun 7, 2013

@sanxiyn yes, closing.

@Aatch Aatch closed this as completed Jun 7, 2013
flip1995 pushed a commit to flip1995/rust that referenced this issue Apr 21, 2022
@bors
Auto merge of rust-lang#8626 - pitaj:format_add_string, r=llogiq
aade96f 
New lint `format_add_strings`

Closes rust-lang#6261

changelog: Added [`format_add_string`]: recommend using `write!` instead of appending the result of  `format!`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sanxiyn @thomaslee @Aatch