Svadev mailing list

[Daniel Aquino <mr.danielaquino AT gmail.com>]

Are you using SAFECode with LLVM 3.0?  On what platform are you using 
SAFECode?  I'm guessing Mac OS X.

clang --version
clang version 3.0 (tags/RELEASE_30/final)
Target: x86_64-apple-darwin12.0.0
Thread model: posix

llvm  revision = 165599

>
> This only happens when I try to use -flto option.

This is either happening because there's a bug in the program or a bug 
in SAFECode.  I'm guessing it's a bug in the SAFECode runtime since 
you're seeing the "Fault!" message.

Can you do the following:

1) Edit runtime/DebugRuntime/PoolAllocatorBitMask.cpp and comment out 
the code that calls sigaction().  This will disable the runtime's 
catching of signals.

There was more than one place.
 

2) Recompile the library, reinstall it (if you used "make install"), and 
recompile your program with SAFECode.

3) Use gdb to run your program.  When it crashes, can you send me the 
stack trace?

-- John T.

All I really see is:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000016
0x00007fff860a8065 in mcount ()

(gdb) bt
#0  0x00007fff860a8065 in mcount ()
#1  0x0000000100437fd7 in DebugPrintf ()


I get the same issue "without" -flto and attempting to use -O4

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000009
0x00007fff860a8065 in mcount ()

(gdb) bt
#0  0x00007fff860a8065 in mcount ()
#1  0x00000001001ce0b4 in DebugPrintf ()


They both take quiet some time to finish and crash.