mirror of
https://github.com/MaskRay/ccls.git
synced 2024-11-21 23:25:07 +00:00
Debugging
parent
9e0a418cae
commit
ea41776be1
16
Debugging.md
16
Debugging.md
@ -24,6 +24,15 @@ You can find stderr output in:
|
||||
`*message*` buffer if `(setq lsp-log-io t)`
|
||||
* VSCode: TODO
|
||||
|
||||
### Indexer issues
|
||||
|
||||
`export CCLS_CRASH_RECOVERY=0` disables clang crash recovery. In case of
|
||||
clangIndex issues, you will not see `clang crashed` in the log file but get a
|
||||
process crash. And if you attach a debugger before it crashes, you can get the
|
||||
stack trace.
|
||||
|
||||
`gdb --args /path/to/ccls -index=/path/to/project`
|
||||
|
||||
### Dump LSP requests/responses
|
||||
|
||||
On Linux:
|
||||
@ -73,13 +82,6 @@ Use `CCLS_TRACEME=s` to `raise(SIGSTOP)`, if `SIGTSTP` does not work.
|
||||
resumes (with a `c` command) if you want ccls to continue running after
|
||||
detaching.
|
||||
|
||||
### Indexer issues
|
||||
|
||||
`export CCLS_CRASH_RECOVERY=0` disables clang crash recovery. In case of
|
||||
clangIndex issues, you will not see `clang crashed` in the log file but get a
|
||||
process crash. And if you attach a debugger before it crashes, you can get the
|
||||
stack trace.
|
||||
|
||||
## Developing
|
||||
|
||||
### Diagnose whether requests are handled correctly
|
||||
|
Loading…
Reference in New Issue
Block a user