Nathan Ridge

> > This is the same underlying issue as [#206](https://github.com/clangd/clangd/issues/206) (and [#1101](https://github.com/clangd/clangd/issues/1101), [#1673](https://github.com/clangd/clangd/issues/1673)): clangd does not support well multiple symbols with the same name in a single workspace. > >...

Could you submit [logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs) taken with `--log=verbose` and covering the period from clangd startup until you get this error?

> My logs are attached The following is potentially relevant: ``` E[04:34:37.351] Scanning modules dependencies for D:/Workspace/ice/src/main.rc failed: error: unable to handle compilation, expected exactly one compiler job in 'D:/Ace/bin/llvm-windres.exe...

> but it would defeat the purpose if the `std.cppm` file is removed My suggestion was that `std.cppm` should be **added** to the compilation database. I'm looking at this error...

Can you try using `--compile-commands-dir` as dicussed in [this FAQ entry](https://clangd.llvm.org/faq#how-do-i-fix-errors-i-get-when-opening-headers-outside-of-my-project-directory)?

> I already have the equivalent of `--compile-commands-dir` set in the `.clangd` file: Unfortunately, they are not equivalent. `.clangd` files are scoped to the directory tree of the directory they...

> 2. When a C++ module is modified, the problem persists for as long, as the file is mapped and processed. Most of the time, it's a few seconds. It...

The crashing codepath is in the clang front-end, i.e. a codepath shared by clangd and clang (the compiler) itself. The first thing I would check is whether the crash is...

> I see - replacing clangd with clang results in the same trace up to `clang::FrontendAction::Execute()`. should I take this issue to llvm/llvm-project? Yes please. Folks following frontend issues there...

Please follow the instructions at https://clangd.llvm.org/troubleshooting.html#getting-stacktraces-from-crashes to obtain a symbolized crash backtrace.