What to do instead of logging?

Suppose our software runs on a device that we can't get to, reasonably, in time. Logging isn't going to help because there isn't anyone around to analyze it and make corrections.

If you couldn't make log files, and the program couldn't depend on a human presence to correct it, then… what?

Maybe we could determine whether some situation is or isn't problematic. Like: input was provided that the program cannot handle. Do we have to log that, or is it OK to ignore?

In case the program runs out of memory, we had better have an operating system governing the faulting program, halting it, clean up the mess, and start it up again. (No, Java, a core dump isn't going to help much either in that case. Worse: it might cause the disk to run out of space. Kthxbye.)

What if the program was supposed to cause a change, but that change never happened? If you don't log that, how would you know? Would the program keep on trying, endlessly, possibly running down the device's energy source, and using up CPU power?

What else can you do instead of logging? Let the program crash? And then what?