[llvm-bugs] [Bug 28378] New: clang frontend command failed due to signal

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=28378

            Bug ID: 28378
           Summary: clang frontend command failed due to signal
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: bashi at chromium.org
                CC: dgregor at apple.com, llvm-bugs at lists.llvm.org
    Classification: Unclassified

I got following error while compiling chromium.

1.      ../../content/browser/browser_main_loop.cc:739:3: current parser token
'{'
2.      ../../content/browser/browser_main_loop.cc:206:1: parsing namespace
'content'
3.      ../../content/browser/browser_main_loop.cc:700:41: parsing function
body 'content::BrowserMainLoop::PreCreateThreads'
4.      ../../content/browser/browser_main_loop.cc:700:41: in compound
statement ('{}')
clang: error: unable to execute command: Segmentation fault (core dumped)
clang: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 3.9.0 (trunk 274142)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir:
/usr/local/google/home/bashi/cr-secondary/src/out/gn-release/../../third_party/llvm-build/Release+Asserts/bin

-- 
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/20160701/7f4d7700/attachment-0001.html>