Svadev mailing list

[John Criswell <criswell AT illinois.edu>]

On 3/5/11 2:43 PM, Matthew Wala wrote:
> It seems that SAFECode silently allows you to modify string literals,
> even when the intended memory operation segfaults the original
> program.
> Shouldn't this be considered a memory safety error?

It depends on what you call a memory safety error.
:)

As far as SAFECode is concerned, writing into a string literal or into 
some other global memory object marked constant is okay because it is 
not an out-of-bounds write.  SAFECode does not enforce read-only 
attributes; it will permit writes to memory that are marked constant, 
for example.  Fortunately, such memory is usually made read-only by the 
OS, so the MMU enforces the read-only attribute of the memory object.

-- John T.


> _______________________________________________
> svadev mailing list
> svadev AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/svadev