> well so far so good, it hasn't crashed using the same conditions as
> before. I'll do some more testing before feeling too certain.
Finger's crossed...
> Checking the Microsoft site for EXCEPTION_ACCESS_VIOLATION (c0000005),
> says: it occurs when a pointer is dereferenced and the pointer points to
> inaccessible memory or a write operation is attempted on read-only memory.
>
> So unless stepping just beyond attrib goes into "inaccessible memory"
> (maybe that's just above the stack), I'm still confused.
That's what I thought could be happening.
David
|