[vwnc] Checking wheter an image got corrupted

Hi all,

does anyone know of a way to check an image for corruption --  
something like a file system check for objects? I suspect a device  
driver API (via DLLCC) to slowly corrupt my image, which starts to  
behave strangely after a while.

Traversing all objects in memory and looking for invalid  
"pointers" (i.e. corrupted objects) should be a viable way to go, but  
I have no idea how to achieve this. Can ImageWriter do that?

Andre
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

On Apr 6, 2008, at 11:31 AM, Andre Schnoor wrote:
That could be one way to go, I'd say just try it (corrupt an image  
manually and see what the ImageWriter does with it).

Another way would be to have the VM do it, compile a VM with debug  
asserts turned on and use that.
The advantage of using the VM for this is that it also checks a lot of  
object types - not just that pointers point to objects.

You may also want to think of ways to discern *what* is being  
corrupted; is it object memory or the memory used by the dll?


Good luck hunting this down,

R
-



>
>
> Andre
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

On Apr 6, 2008, at 2:18 PM, Reinout Heeck wrote:
>
> Another way would be to have the VM do it, compile a VM with debug
> asserts turned on and use that.
> The advantage of using the VM for this is that it also checks a lot of
> object types - not just that pointers point to objects.


Once on this track you may also want to instrument your DLLCC calls to  
do a full GC after each call so the Vm's asserts 'fail fast'.

R
-


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc