#18827 - JL - Tue Apr 06, 2004 4:03 pm
Hi guys,
I'm using vba for debugging and I ran into the following (from trace.log):
.
.
.
DMA3: s=02000030 d=07000000 c=8400 bytes=00000400
Illegal byte read: 0000000c at 08006a64
Illegal byte read: 0000000c at 08006a64
Illegal byte read: 0000000c at 08006a64
Now, by checking out what's at 0x08006a64 I found out that all I'm doing is calling a (virtual) method from a C++ class, like this:
myObjects[j]->setvisibility(myObjects[0]);
(j is valid, ofcourse... so are the object arrays).
When I remove the call to that function, the illegal reads disappear. So, my question is, what's wrong here? What does illegal read mean in this context, is something not aligned correctly? Can anyone shed some light on this? Thanks in advance!
Grtz,
Niels
I'm using vba for debugging and I ran into the following (from trace.log):
.
.
.
DMA3: s=02000030 d=07000000 c=8400 bytes=00000400
Illegal byte read: 0000000c at 08006a64
Illegal byte read: 0000000c at 08006a64
Illegal byte read: 0000000c at 08006a64
Now, by checking out what's at 0x08006a64 I found out that all I'm doing is calling a (virtual) method from a C++ class, like this:
myObjects[j]->setvisibility(myObjects[0]);
(j is valid, ofcourse... so are the object arrays).
When I remove the call to that function, the illegal reads disappear. So, my question is, what's wrong here? What does illegal read mean in this context, is something not aligned correctly? Can anyone shed some light on this? Thanks in advance!
Grtz,
Niels