Here's a real example that truly does leak information to a user, even in Fil-C, due to a user-provided out-of-bounds offset.
If your "safe C" system doesn’t protect against "valid pointer bad offset," then it isn’t actually enforcing memory safety.
gist.github.com/unixpickle/4…