Re: how to avoid a memset() optimization

Of course, there is also the difficulty in ensuring that a copy of the
data in question doesn't remain in backing store (e.g., a page file) because
on process rundown, the pages being deleted aren't written back but sent to
the free list right away. I'm sure of reading of some criminal investigations
yielding evidence by analysis of such files. (Windows is of course also famous
for leaving temporary files around almost indefinitely.)


Oh, and what about the copies in the OS's I/O buffers? or the memory of
attached I/O devices that were used to enter/read them?


This problem isn't easy to solve at all.


Jan

Return to the comp.compilers page.
Search the comp.compilers archives again.