[llvm-bugs] [Bug 41195] New: clangd-indexer fails using concurrency with multiple directories
via llvm-bugs
llvm-bugs at lists.llvm.org
Fri Mar 22 02:30:08 PDT 2019
https://bugs.llvm.org/show_bug.cgi?id=41195
Bug ID: 41195
Summary: clangd-indexer fails using concurrency with multiple
directories
Product: clang-tools-extra
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: clangd
Assignee: unassignedclangbugs at nondot.org
Reporter: shanehird at gmail.com
CC: llvm-bugs at lists.llvm.org
I reported this to the mailing list but it may be more appropriate here.
clangd-indexer does not seem to handle compile_commands.json with different
directories. I am able to workaround the problem by passing
'-execute-concurrency=1'.
It seems to work ok with a single directory (i.e with just 'abc' from the
example below), but fails if there are multiple, as in the example below.
I am working with revision 356635 of clangd.
With a directory structure of:
./
./abc
./abc/test.h
./abc/test.cc
./def
./def/ytest.h
./def/xtest.cc
./compile_commands.json
And a compile_commands.json of:
[
{
"arguments": [
"g++",
"-c",
"-o",
"test.o",
"test.cc"
],
"directory": "/home/test/abc",
"file": "test.cc"
},
{
"arguments": [
"g++",
"-c",
"-o",
"xtest.o",
"xtest.cc"
],
"directory": "/home/test/def",
"file": "xtest.cc"
}
]
I receive the error:
[test]$ clangd-indexer -executor=all-TUs compile_commands.json > clangd.dex
[1/2] Processing file /home/test/abc/test.cc
[2/2] Processing file /home/test/def/xtest.cc
error: no such file or directory: 'test.cc'
error: no input files
error: unable to handle compilation, expected exactly one compiler job in ''
Error while processing /home/test/abc/test.cc.
Failed to run action on /home/test/abc/test.cc
I assume it may be related to a non-thread-safe chdir somewhere in the code.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190322/8ad336d9/attachment.html>
More information about the llvm-bugs
mailing list