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

Repetitive error messages on faulty clangd start #408

Closed
ghentschke opened this issue Jan 31, 2025 · 0 comments · Fixed by #411
Closed

Repetitive error messages on faulty clangd start #408

ghentschke opened this issue Jan 31, 2025 · 0 comments · Fixed by #411
Assignees
@ghentschke
Labels
bug Something isn't working

Comments

@ghentschke
Copy link
Contributor

When the clangd has configuration errors, the user gets confronted with repetitive error messages when the LS has been triggered to start by LSP4E:

Image

Reason: clangd gets started but exits immediately with an error. This could be endless becuase LSP4E restarts clangd again and again ....

Steps to reproduce:
Create a faulty clangd config, and press Apply and Close

Image
@ghentschke ghentschke self-assigned this Jan 31, 2025
@ghentschke ghentschke added the bug Something isn't working label Jan 31, 2025
ghentschke added a commit to ghentschke/eclipse-cdt-lsp that referenced this issue Feb 1, 2025
@ghentschke
[eclipse-cdt#408] add clangd command line options validator
a2c0ad7 
if clangd version >= 11, then the clangd binary will be called with
configured command line options plus --check and --log=error.
If the stderr stream remains empty everything is fine and we can go on.
Otherwise we through an IOException in the start() method. This leads to
an error dialog with the strings returned from stderr stream.

fixes eclipse-cdt#408
ghentschke added a commit to ghentschke/eclipse-cdt-lsp that referenced this issue Feb 1, 2025
@ghentschke
[eclipse-cdt#408] add clangd command line options validator
fb90803 
if clangd version >= 11, then the clangd binary will be called with
configured command line options plus --check and --log=error.
If the stderr stream remains empty everything is fine and we can go on.
Otherwise we through an IOException in the start() method. This leads to
an error dialog with the strings returned from stderr stream.

fixes eclipse-cdt#408
@ghentschke ghentschke mentioned this issue Feb 1, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ghentschke ghentschke

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#408] add clangd command line options validator ghentschke/eclipse-cdt-lsp
1 participant
@ghentschke