Svadev mailing list

[Matthew Wala <wala1 AT illinois.edu>]

Hi everyone:
The most recent version of SAFECode is giving me trouble with very
simple test cases.

For instance, the program

int main()
{
  int i[100];
  i[101] = 10;
  return 0;
}


when instrumented and run results in the following output:

SAFECode:Violation Type 0x6 when accessing  0x617934 at IP=0x401fc0

=======+++++++    SAFECODE RUNTIME ALERT +++++++=======
= Error type                            :       Load/Store Error
= Faulting pointer                      :       0x617934
= Program counter                       :       0x401fc0
= Fault PC Source                       :       main:6
=
= Object allocated at PC                :       0x401ef4
= Allocated in Source File              :       main:1
= Object allocation sequence number     :       1
= Object start                          :       0x6177a0
= Object length                         :       0x64
SAFECode: Fault!
SAFECode:Violation Type 0x9 when accessing  0xc0000001 at IP=0x411b64

=======+++++++    SAFECODE RUNTIME ALERT +++++++=======
= Error type                            :       Uninitialized/NULL Pointer 
Error
= Faulting pointer                      :       0xc0000001
= Program counter                       :       0x411b64
= Fault PC Source                       :       <unknown>:0
SAFECode: Fault!
SAFECode:Violation Type 0x9 when accessing  0xc0000001 at IP=0x411b64

=======+++++++    SAFECODE RUNTIME ALERT +++++++=======
= Error type                            :       Uninitialized/NULL Pointer 
Error
= Faulting pointer                      :       0xc0000001
= Program counter                       :       0x411b64
= Fault PC Source                       :       <unknown>:0
SAFECode: Fault!
SAFECode:Violation Type 0x9 when accessing  0xc0000001 at IP=0x411b64

The last Unitialized / NULL Pointer Error statement is repeated without end.
Is there an explanation for this behavior and how can I get it to work 
properly?

Thanks,
Matt