|
From: Banibrata D. <du...@in...> - 2004-05-07 19:12:55
|
hi, i've made sure in my code (which is not too big) that there are no mismatched new/delete's i.e. i use only new (although placement new, i.e., new(std::nothrow) for allocation), and delete for deallocation (of non-array type of object) only. inspire of that i see this error, which is then followed by "Address 0x3D4A0AE0 is 0 bytes inside a block of size 48 alloc'd" and this happens consistently. could this problem happen due my deleting the pointer twice (by mistake) ? thanks & regards, Banibrata Dutta Hewlett-Packard ISO Pvt. Ltd, 29, Cunningham Road, Bangalore - 560052, India. Tel: +91-80-22051796 |
|
From: Nicholas N. <nj...@ca...> - 2004-05-07 22:20:49
|
On Sat, 8 May 2004, Banibrata Dutta wrote: > i've made sure in my code (which is not too big) that there are no > mismatched new/delete's i.e. i use only new (although placement new, > i.e., new(std::nothrow) for allocation), and delete for deallocation (of > non-array type of object) only. inspire of that i see this error, which > is then followed by "Address 0x3D4A0AE0 is 0 bytes inside a block of > size 48 alloc'd" and this happens consistently. could this problem > happen due my deleting the pointer twice (by mistake) ? Deleting the pointer twice would probably give an obvious error message. Can you give more detail about the problem, ie. the actual error message? That might let someone give a more useful answer. N |