bloody memory bug

there is 2 things that you could test:

-run until the line of creation and see what is the number inside the size. if it is odd, then probrably there is the error.
-try to delete the [] from the delete [] darray. Chack if it works


Techno Grooves

Can a pointer return a true or false statement ? I mean r u allowed to put pointers in boolean expressions ? Because thats what u r doing: --------> if(darray)

______________________________
My Website: [link]www.antondev.tk[/link]
or directly at http://home.attbi.com/~antonweb/
"I''ve read about...doom being used to manage unix programs(you "kill" the processes)" dede

Yes, you can test pointers, or any other variables against 0.

Height Map Editor | Eternal Lands | Fast User Directory

quote:

---

-run until the line of creation and see what is the number inside the size. if it is odd, then probrably there is the error.

---

Would it really give an error if it were odd? Why?

quote:

---

Original post by llvllatrix
Would it really give an error if it were odd? Why?

---

I think Filami means "odd" as in "unusual".

I don''t see how that will give an error if the type was basic. However, if it is one of your class types then your error might be somewhere else.

Run your debugger to find the exact line where your program gives the error.

try doing this:

type *darray = NULL;
darray = new type[SIZE];
if(darray) delete[] darray;

ive noticed that if the "new type[SIZE]" part fails, it doesnt set darray to NULL. thus darray will alway point to a random non-null memory address.

Its the oddest thing. Actually the code is in a milkshape exporter that i wrote. Its just for this one model that it screws up. Ultimately, the file it produces is fine. Its just that for this one file, when i try to delete the triangle array, i get the illegal opperation.

I got the file though...really all i cared about but i was just wondering if there was some wierd thing i didn''t know about that was messing with my code...probably just my pc - its starting to die now, going to have to format soon

sometimes, if you write past the end of a dynamically allocated array, the delete operator will crash.


// Website // Google // GameDev // NeHe // MSDN // OpenGL Extensions //