[llvm-bugs] [Bug 41003] New: Reproducible clangd crash
via llvm-bugs
llvm-bugs at lists.llvm.org
Thu Mar 7 19:58:46 PST 2019
https://bugs.llvm.org/show_bug.cgi?id=41003
Bug ID: 41003
Summary: Reproducible clangd crash
Product: clang-tools-extra
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: clangd
Assignee: unassignedclangbugs at nondot.org
Reporter: phosek at chromium.org
CC: llvm-bugs at lists.llvm.org
Created attachment 21576
--> https://bugs.llvm.org/attachment.cgi?id=21576&action=edit
VSCode logs
One of our developers have been seeing the following clangd crash when using
VSCode:
clangd:
/b/s/w/ir/kitchen-workdir/llvm-project/clang-tools-extra/clangd/Selection.cpp:201:
bool clang::clangd::(anonymous namespace)::SelectionVisitor::nodesCoverRange(
llvm::ArrayRef<const Node *>, unsigned int, unsigned int): Assertion
`R.isTokenRange()' failed.
The crash can be reproduced using the files in
https://fuchsia-review.googlesource.com/c/fuchsia/+/258851. For the crash to
happen, it's necessary need to have two editors open side-by-side on these
exact files: page_storage_impl.cc, live_commit_tracker.cc
The logs from VSCode are attached as well.
--
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/20190308/68d93102/attachment.html>
More information about the llvm-bugs
mailing list