xzhangxian1008

> In my experience, this usually happens when the index is out of date, for example when you have pulled the code from upstream while clangd is running. Restating clangd...

> Yes, this match the behaviour I observed, but Block.cpp:183 is not the correct position.

> Which file and line is the expected result? DecimalComparison.h:204 is the expected result.(may be line number is not 204, as the codes have little changed in my current workspace)

> Is there something in Block.cpp that clangd might confuse for the definition you're looking for, like a function with the same name, or a redeclaration of the same function?...

> Block.cpp I believe this is unrelated to `compile_commands.json`. Because my clangd13.0.0 could jump to the correct position while clangd15.0.7 couldn't with the same `compile_commands.json` ``` { "directory": "/DATA/disk3/xzx/tiflash/build/dbms", "command":...

> Could you show a log (similar to the one in the first comment) from clangd 13.0? here [clangd13.txt](https://github.com/clangd/vscode-clangd/files/12434825/clangd13.txt)

> `compile command` you mean cmake command or clang command? Is there more information you need?

> I would however be curious to know if this happens for you with a different project, or on a different machine. I will try it.

> I would however be curious to know if this happens for you with a different project, or on a different machine. I tried the same project on another machine,...

/cc @wshwsh12