Re: c++ debugging
I have a question I should know the answer to.
I've delivered a working set of c++ libraries/dlls that have been
By the time they are DLLs, most of the traces of their being "C++"
have disappeared, haven't they?
fully tested and validated. Now my problem is that somebody else has
been furiously fixing memory leaks and what not in another DLL that is
used by my own. I suddenly find myself in the situation where MY dll's
are now crashing out and I'm fairly sure, that the fixes in the other
DLL have hosed my stuff. I'm thinking its trampling on memory or
corrupting the heap.
So far no relevance to this newsgroup's main topic...
I would like to determine if this is the case. Though I'm not sure how
to go about it. All of a sudden, all my pointers are pointing to
invalid data/memory and I'm getting crashest with even the SIMPLEST of
OK, I noticed the word "pointers". Doesn't make it on topic yet...
Can anybody tell me whats the best way to go about determining if
memory is been corrupted.
Some kind of tool should help you. Tools are OS-specific, most often.
You can probably find a good memory manager with some debugging
capabilities, but then the entire application has to use it. Again,
not enough specificity to be posted in comp.lang.c++...
I feel bad asking this as I should really
know the answer! :( Ideally I'd like to know precisely the point in
time that somebody writes to MY memory or corrupts it. I've put
breakpoints in dtors to see if anybody is explitly deleting my objects
but thats come up blank.
<shrug> Debugging is not defined in the language...
I'm working in a MS environment, but thats not realy important here.
Yes, it is! You bet your sweet ... it is! Post to the newsgroup
that deals with programming "MS environment" and ask about memory
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask