Nathan Ridge

> Using this build I get a crash with `MallocScribble` enabled. Here's an excerpt from the crash log: This clangd 16 crash is in a different place in the code...

> I downloaded the indicated snapshot (https://github.com/clangd/clangd/releases/tag/snapshot_20231210) and I'm seeing this crash: This one is again in a different place, occuring during background indexing. So, it looks like the async...

It's an interesting idea, though I'll note that if you have such an option-mapping executable, presumably it's straightforward to combine it with a json processing tool like `jq` to post-process...

https://github.com/clangd/clangd/issues/1871 was about a crash in the same function (`ASTContext::getTypeInfoImpl`), but interestingly that one was reported as affecting clangd 16 but being fixed on trunk. It could be a different...

Looking at the code, the message "Transport error: Got signal, shutting down" is printed when the clangd process receives a SIGINT [signal](https://developer.apple.com/library/archive/documentation/System/Conceptual/ManPages_iPhoneOS/man3/signal.3.html). I've no idea who might be sending that...

See also https://github.com/llvm/llvm-project/issues/69690 for another report of what looks like potentially the same regression from clangd 16 to clangd 17.

My first thought was that `X a;` is not a valid usage of a template-name `X`. But since C++17, it is (the template arguments could be deduced using [CTAD](https://en.cppreference.com/w/cpp/language/class_template_argument_deduction)).

> I am unable to get response files to work (at least on Windows) when added to my `config.yaml`, like below: > > ```yaml > CompileFlags: > Add: [ "@C:\\absolute\\path\\to\\response-file.txt"...

> is there any reason not to also parse response files found in `CompileFlags:` once clangd gets there? No, I think that would be a reasonable enhancement.

> Cool 🙂 Would you like me to open a separate feature request for that, or is this thread sufficient? I went ahead and filed one at https://github.com/clangd/clangd/issues/2079. For this...