Boris Staletic
Boris Staletic
Maybe, but we can only guess with absolutely no debugging information provided so far. What are you flags exactly? What is the content of the cquery's log? What code shows...
By default cquery only updates the index once it receives the `didSave` notification. Could that explain the stale file representation in the index?
Here's the link to the wiki: https://github.com/cquery-project/cquery/wiki/Debugging#dump-lsp-requestsresponses You'll have to comb through all the requests and messages.
@trond-snekvik I'm starting to think your issue is unrelated to @svorobiev's. I could be totally wrong. @svorobiev That indeed sounds like the notifications are firing and cquery is picking them...
I'm not a vscode user, so you'll have to read the wiki: https://github.com/cquery-project/cquery/wiki/Visual-Studio-Code#setting-up-the-extension
I wonder what's the output of `nm ./cquery | grep pthread_setname_np`. For me that's: U pthread_setname_np@@GLIBC_2.12 What it says is, there is no fixed memory address offset for the symbol...
Alright, so what is the output of cmake configuration without the explicit `-pthread`?
@DaanDeMeyer That bug was fixed in cmake 3.4. @jamescookmd The one before `cmake --build`. Probably just `cmake ..`, but in a clean build directory.
From your output: ``` -- Looking for C++ include pthread.h -- Looking for C++ include pthread.h - found -- Looking for pthread_create -- Looking for pthread_create - found -- Found...
As far as I know, it doesn't. Otherwise, ycmd would work on cygwin.