Re: Pirates of Silicon Valley

[mudboy@pacbell.net]

On Mon, 05 Jul 1999 14:25:02 +1000, dale@cs.rmit.edu.au (Dale
Stanbrough) wrote:

>Mike Pike wrote:
>
>" COM objects do not expose member 
>  data. You can only access it via an interface method or property."
>
>If the COM object lives in the same address space, and it is not
>protected (e.g. marked read only by the MMU/o/s), it can -still- be
>splattered by an errant bit of code, whether it is hiding behind a
>(source code level) an interface or not.
>
>Dale


Absolutely.... But you cannot DIRECTLY corrupt member data inside a
COM object that runs in-proc. 

In fact, since you really don't know where the member data lives in
the memory map (because the interface is a handle), your "chance" of
hitting or corrupting member data in any com object is very small...

you might as well write this program..

	long l
	unsigned char *p;
	for (l=1; l < 0xFFFFFFFF; l++)
	{
		p = (unsigned char *) l;
		*p = 0;
	}

NT can and will protect against this.... you also run the risk of
ruining in-proc COM objects...

smentzer@pacbell.net