![]() |
【转帖】memory deallocation problem
memory deallocation problem?
memory deallocation problem? hi all i have created a standalone executable from the exalloc example in the latest dwgdirect distribution, and have linked to our memory debugging code. it basically checks to see if memory is being deallocated correctly. it is currently reporting an error caused by the delete operator being used to free memory that has been allocated by the new[] operator. to replicate the problem download ftp.surpac.com/incoming/dwgdirectparser.zip (it's about 3.5mb) and run... vect.exe "truck model.dwg" output.txt ...it should load the file and popup an error after processing for a few seconds. can someone with access to the source code have a look to see what is causing it please? i have added the build directory to the zip also if you want to build it yourself, just tweak makefile.gnu. everything seems to run ok in a production build but i don't know if this will cause any side-effects later on? cheers andy surpac minex group hello, i can't see the file at ftp.surpac.com/incoming (really, i don't see any files there) you may mail it directly to me: vkalinin at softdev dot spb dot ru vladimir quote: originally posted by wvk hello, i can't see the file at ftp.surpac.com/incoming (really, i don't see any files there) you may mail it directly to me: vkalinin at softdev dot spb dot ru vladimir sorry, i should have mentioned that you won't be able to get a directory listing but you can still do an ftp get. i'll mail it to you now... thanks i implemented similar functionality in odalloc and discovered 3 places in our code where memory was allocated via new[] and freed via delete. thank you for pointing out the problem. |
所有的时间均为北京时间。 现在的时间是 04:22 PM. |