Svadev mailing list

[John Criswell <criswell AT illinois.edu>]

On 1/31/11 9:51 AM, Divya Muthukumaran wrote:
> Hi,
>
>
> I am just trying out SafeCode after reading the paper. I ran the sc 
> tool on a simple program with an out of bounds error and I get the 
> following output when I run the executable.
>
> SAFECode:Violation Type 0x4 when accessing  0x80d3b4c at IP=0x804a979
>
> I had compiled the program with llvm-gcc with the -g option. Do I have 
> to do anything else for it to print the source file and line number?

Which version of the sc tool are you using (the release_26 branch or 
mainline)?

You might need to use the --enable-debuginfo option if it's an older 
version of the sc tool, but I thought I had changed the tool to use 
debug information by default.

The error report should look something like this:

=======+++++++    SAFECODE RUNTIME ALERT +++++++=======
= Error type                            :    Load/Store Error
= Faulting pointer                      :    0x47654036edd0
= Program counter                       :    0x1000546ff
= Fault PC Source                       : <unknown>:0

On a related note, the interface for using debug information changed 
between LLVM 2.6 and LLVM 2.7.  I haven't yet updated mainline SAFECode 
to use the new debug info APIs in LLVM 2.7, so it prints function name 
and an ID number instead of source line/source file at present.

-- John T.

> Thanks,
> Divya