Just FYI (I just tried this with the ³new² Xcode6-DP version of Clang++ and it does indeed work on that version.
/Users/ErnieE -> sudo xcode-select -s /Applications/Xcode6-Beta.app/ /Users/ErnieE -> clang++ -g -std=c++11 crash.cpp /Users/ErnieE -> The version in XCode5 causes the same issue. /Users/ErnieE -> sudo xcode-select -s /Applications/Xcode.app/ /Users/ErnieE -> xcodebuild -version Xcode 5.1.1 Build version 5B1008 /Users/ErnieE -> clang++ -g -std=c++11 crash.cpp Stack dump: 0. Program arguments: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolch ain/usr/bin/clang -cc1 -triple x86_64-apple-macosx10.9.0 -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name crash.cpp -mrelocation-model pic -pic-level 2 -mdisable-fp-elim -masm-verbose -munwind-tables -target-cpu core2 -target-linker-version 236.3 -gdwarf-2 -resource-dir /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolch ain/usr/bin/../lib/clang/5.1 -stdlib=libc++ -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /Users/ErnieE -ferror-limit 19 -fmessage-length 150 -stack-protector 1 -mstackrealign -fblocks -fobjc-runtime=macosx-10.9.0 -fencode-extended-block-signature -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -vectorize-slp -o /var/folders/_j/6wgc14x52lldvq_38tt3yjjm0000gn/T/crash-05a732.o -x c++ crash.cpp 1. crash.cpp:29:1: current parser token 'int' 2. crash.cpp:27:11: LLVM IR generation of declaration 'boom' 3. crash.cpp:27:11: Generating code for declaration 'boom' clang: error: unable to execute command: Segmentation fault: 11 clang: error: clang frontend command failed due to signal (use -v to see invocation) Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.2.0 Thread model: posix clang: note: diagnostic msg: PLEASE submit a bug report to http://developer.apple.com/bugreporter/ and include the crash backtrace, preprocessed source, and associated run script. clang: note: diagnostic msg: ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: /var/folders/_j/6wgc14x52lldvq_38tt3yjjm0000gn/T/crash-61b51e.cpp clang: note: diagnostic msg: /var/folders/_j/6wgc14x52lldvq_38tt3yjjm0000gn/T/crash-61b51e.sh clang: note: diagnostic msg: ******************** /Users/ErnieE -> In the close of the bug you mention that the version I am running isn¹t ³valid.² I followed the directions here: http://llvm.org/apt/ for both Stable and Development branches. Is there a ³better² version that I should acquire? Am I missing something important? I wouldn¹t have filed the issue if Xcode6 had been available and it had been shown to be fixed. I encountered this with the Linux versions (3.4 and 3.5) installed via both the stable and development branch versions as directed via the link above. I am GLAD this is fixed, but I¹d like to know if there is a BETTER approach I can follow so I don¹t ³waste² more time in the future. (Both yours AND mine.) I am sorry if responding to this ³re-opens² the issue. That is NOT my intent, but the instructions say to reply to the email. I am ecstatic that this effort is happening and I hope that the project doesn¹t get co-opted by any single vendor. Thanks! [email protected] On 6/11/14, 9:21 AM, "Debian Bug Tracking System" <[email protected]> wrote: >This is an automatic notification regarding your Bug report >which was filed against the clang-3.5 package: > >#749830: /usr/bin/clang: clang++ crash when -g option used on template >with pointer to member in signature > >It has been closed by Sylvestre Ledru <[email protected]>. > >Their explanation is attached below along with your original report. >If this explanation is unsatisfactory and you have not received a >better one in a separate message then please contact Sylvestre Ledru ><[email protected]> by >replying to this email. > > >-- >749830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749830 >Debian Bug Tracking System >Contact [email protected] with problems -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
