Memory corruption rant.
Jesse Phillips
jessekphillips+D at gmail.com
Wed May 18 09:37:33 PDT 2011
Kagamin Wrote:
> Jesse Phillips Wrote:
>
> > writeln("I"m still ok")
> > writeln(myObject is null); // Crash with access violation
>
> try
> writeln("I'm still ok");
> writeln(0);
> writeln(false);
All those print.
> > I'm not even accessing myObject, I'm just asking if it has a value it shouldn't!
>
> Did you try a debugger?
> At least, you can see where it crashes.
I'm pretty sure it crashes any time a Look at an object. I placed a print statement after where I said it crashes and it doesn't print. So while it isn't definitive, I'm pretty confident.
On top of that with -g Optlink will fail with:
Unexpected OPTLINK Termination at EIP=0042781B
EAX=00000000 EBX=00000204 ECX=000000E2 EDX=04020B9E ESI=0043E664 EDI=01324000 EBP=0012FFF0 ESP=0012FF70 FIrst=00402000
Again, without a good test case this is probably useless, and I'll look into updating dmd/optlink when I update my libraries for the new compiler (DUI, LuaD).
More information about the Digitalmars-d-learn
mailing list