Actually the failure is in the compilation...
# clang -DHAVE_CONFIG_H -I. -I../include -I../include -I/sw/include
-I../include -g -O2 -MT pr0be.lo -MD -MP -MF .deps/pr0be.Tpo -c
filter/measure/pr0be.c -fno-common -DPIC -o .libs/pr0be.o
0 clang 0x0000000104498422 _ZL15PrintStackTracePv + 34
1 clang 0x00000001044988a9 _ZL13SignalHandleri + 553
2 libsystem_c.dylib 0x00007fff9a800cfa _sigtramp + 26
3 libsystem_c.dylib 0x00007fff9a7ff1a4 malloc + 44
4 clang 0x00000001037c3cd8
_ZL13LowerConstantPKN4llvm8ConstantERNS_10AsmPrinterE + 1304
5 clang 0x00000001037c3cd8
_ZL13LowerConstantPKN4llvm8ConstantERNS_10AsmPrinterE + 1304
6 clang 0x00000001037c3318
_ZL22EmitGlobalConstantImplPKN4llvm8ConstantEjRNS_10AsmPrinterE + 3128
7 clang 0x00000001037c17d8
llvm::AsmPrinter::EmitGlobalVariable(llvm::GlobalVariable const*) + 1736
8 clang 0x00000001037c0c6f
llvm::AsmPrinter::doFinalization(llvm::Module&) + 79
9 clang 0x000000010373a507
llvm::FPPassManager::runOnModule(llvm::Module&) + 231
10 clang 0x00000001037358c1
llvm::MPPassManager::runOnModule(llvm::Module&) + 289
11 clang 0x00000001037352c5
llvm::PassManagerImpl::run(llvm::Module&) + 277
12 clang 0x00000001037351ad llvm::PassManager::run(llvm::Module&) +
13
13 clang 0x0000000103713e3c
clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::CodeGenOptions
const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::Module*,
clang::BackendAction, llvm::raw_ostream*) + 4508
14 clang 0x0000000103711641
clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) + 513
15 clang 0x00000001035dd0f6 clang::ParseAST(clang::Sema&, bool) +
406
16 clang 0x00000001035dbbd7 clang::CodeGenAction::ExecuteAction() +
855
17 clang 0x00000001035ae13f
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) + 879
18 clang 0x00000001035acdcb
clang::ExecuteCompilerInvocation(clang::CompilerInstance*) + 2683
19 clang 0x000000010359f5ce cc1_main(char const**, char const**,
char const*, void*) + 5086
20 clang 0x0000000103579dd8 main + 648
21 clang 0x0000000103579b44 start + 52
22 clang 0x0000000000000043 start + 18446744069358511411
Stack dump:
0. Program arguments: /usr/bin/clang -cc1 -triple
x86_64-apple-macosx10.7.4 -emit-obj -disable-free -disable-llvm-verifier
-main-file-name pr0be.c -pic-level 1 -mdisable-fp-elim -relaxed-aliasing
-masm-verbose -munwind-tables -target-cpu core2 -target-linker-version 128.2 -g
-coverage-file .libs/pr0be.o -resource-dir /usr/bin/../lib/clang/3.1
-dependency-file .deps/pr0be.Tpo -sys-header-deps -MP -MT pr0be.lo -D
HAVE_CONFIG_H -D PIC -I . -I ../include -I ../include -I /sw/include -I
../include -fmodule-cache-path /var/tmp/clang-module-cache -O2
-fdebug-compilation-dir /sw/src/fink.build/frei0r-dev-1.3-1/frei0r-1.3/src
-ferror-limit 19 -fmessage-length 173 -stack-protector 1 -fblocks
-fobjc-runtime-has-arc -fobjc-runtime-has-weak -fobjc-dispatch-method=mixed
-fno-common -fdiagnostics-show-option -fcolor-diagnostics -o .libs/pr0be.o -x c
filter/measure/pr0be.c
1. <eof> parser at end of file
2. Code generation
3. Running pass 'Function Pass Manager' on module 'filter/measure/pr0be.c'.
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal 2 (use -v to see
invocation)
clang: note: diagnostic msg: Please submit a bug report to
http://developer.apple.com/bugreporter/ and include command line arguments and
all diagnostic information.
clang: note: diagnostic msg: Preprocessed source(s) and associated run
script(s) are located at:
clang: note: diagnostic msg: /tmp/pr0be-qx6Qf9.i
clang: note: diagnostic msg: /tmp/pr0be-qx6Qf9.sh
This appears to be a bug in clang 3.1svn of Xcode 4.3.3 because if the clang
from our llvm31 package is used,
the compiler crash doesn't occur. Also the compiler crash can be suppressed by
lowering the optimization for that
file to -O1 from -O2.
Jack
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
