Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upwindows rls stderr: thread 'main' has overflowed its stack #838
Comments
alexheretic
referenced this issue
Apr 26, 2018
Closed
stderr thread 'main' has overflowed its stack #75
This comment has been minimized.
This comment has been minimized.
|
Do you have a stack trace? I'm aware of Racer causing this problem sometimes, I've not seen it happen due to the compiler or RLS. Could test by disabling Racer completion and seeing if it reproduces. |
This comment has been minimized.
This comment has been minimized.
dannyfritz
commented
Apr 30, 2018
•
|
Can you provide me more information about disabling racer and retrying it? The output you see above is all I've seen too when running No stack trace from what I can tell. I do have With |
This comment has been minimized.
This comment has been minimized.
In your user settings, set |
This comment has been minimized.
This comment has been minimized.
dannyfritz
commented
May 2, 2018
|
Adding |
This comment has been minimized.
This comment has been minimized.
|
Since this is/was reproduced by Running the steps on the latest nighty produces a new error It still
|
This comment has been minimized.
This comment has been minimized.
|
Having the exact same issue with a |
nrc
added
the
bug
label
May 23, 2018
This comment has been minimized.
This comment has been minimized.
|
Using RLS on the command line with today's nightly Rust and RLS master I get a bunch of compile errors, but no panic and no stack overflow. |
This comment has been minimized.
This comment has been minimized.
|
In VSCode I'm also not seeing a panic or stack overflow but I am seeing the errors in logs, but no report to the user. |
This comment has been minimized.
This comment has been minimized.
|
Whoops, missed that this was Windows only, that would explain why I'm not seeing it. |
This comment has been minimized.
This comment has been minimized.
dannyfritz
commented
May 23, 2018
•
|
I'm getting the same error with |
This comment has been minimized.
This comment has been minimized.
|
If someone who can reproduce on Windows could run a debug build of the RLS and get a backtrace, that would be really useful |
This comment has been minimized.
This comment has been minimized.
dannyfritz
commented
May 23, 2018
•
|
I cloned this repo and compiled
|
This comment has been minimized.
This comment has been minimized.
dannyfritz
commented
May 23, 2018
•
|
Ran it in
|
This comment has been minimized.
This comment has been minimized.
dannyfritz
commented
May 23, 2018
|
I don't have a |
This comment has been minimized.
This comment has been minimized.
Awesome, thank you! |
This comment has been minimized.
This comment has been minimized.
|
@dannyfritz could you run again please? But add the following before https://github.com/rust-lang-nursery/rls/blob/master/src/server/mod.rs#L391:
|
This comment has been minimized.
This comment has been minimized.
dannyfritz
commented
May 24, 2018
•
|
|
This comment has been minimized.
This comment has been minimized.
|
The After resolving the UNC path thing (I'll raise a pr) we're back to Output (with InitializeResult contents removed):
Sometimes at this point windows will notify me that rls.exe has crashed. Sometimes the output prints a little more, but rls is still kaput.
|
alexheretic commentedApr 26, 2018
Initially reported rust-lang/atom-ide-rust#75. Soon after starting rls reports
thread 'main' has overflowed its stackon stderr. This seems to be the cause of rls not working for this project.Steps to reproduce
git clone https://github.com/dannyfritz/learn-gliumrustup run nightly rls --cliThis produces