correction of the heap
ssylee
program works well, except upon exiting the program, I got the
following error:
Windows has triggered a breakpoint in matx_migrate.exe.
This may be due to a corruption of the heap, and indicates a bug in
matx_migrate.exe or any of the DLLs it has loaded.
The output window may have more diagnostic information
What typically would make me see such an error? Memory leak?
Victor Bazarov
Double deletion of a pointer... Buffer overrun... Random uninitialised
pointer dereferenced...
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
ssylee
Ian Collins
It could be any number of things, a couple of common causes of heap
corruption are writing though a pointer that has been freed and writing
past the end of a bloc.
Review your code and use whatever bounds checker your tools support.
--
Ian Collins
Leandro Melo
If your program is not complex and doesn't have several modules
involved, I'd guess that you're trying to delete an object twice (the
second time being when the destructor is automatically invoked).
--
Leandro T. C. Melo.
ssylee
I'm still not sure what's happening with my code. I tried to debug it
by commenting out blocks of the code, and then uncommenting one
section at a time while I run each debug trial. I have noticed that
one of the functions that I have implemented may have been making the
difference between whether that error shows up or not. Would be
appreciated for suggestions if that leads closer to anywhere. Thanks.
ssylee
This is going to be my last post on the topic. Apparently, there was a
buffer overrun. After I made some minor changes to an object
instantiation, that problem is gone.
gw7...@aol.com
> This is going to be my last post on the topic. Apparently, there was a
> buffer overrun. After I made some minor changes to an object
> instantiation, that problem is gone.
"Apparently"?? I'd recommend having a look though the code as it was,
and as it is now, to check that there was a problem before and that it
is now fixed. For one thing, this will make sure that the problem has
indeed gone, and is not simply lurking there ready to find a new way
of showing itself, and also, you may think of other bits of the
program which also need checking.
Hope this helps.
Paul.
Rolf Magnus
As a general rule of thumb: A bug isn't fixed as long as you don't know
exactly why it's fixed.
Pete Becker
Another way to put it is bugs that go away by themselves come back by
themselves.
--
Pete
Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of "The
Standard C++ Library Extensions: a Tutorial and Reference
(www.petebecker.com/tr1book)