Heap damage

  • Thread starter Thread starter Monica R.
  • Start date Start date
M

Monica R.

Hi everyone! I've got a problem with a windows forms application. I
modified source code, but when I ran the application the new code was
simply ignored. Then I tried and debug, but debug points were also
ignored. VS finally showed the following message:

Windows generated a debug point in your application. This may be
caused by a hep damage and indicates an error in your application or
in one of DLLs your project loaded.

I never encountered a similar problem and I need help.
Thank you!
 
Hard to guess what you did but clearly you changed more than you thought you
did. First, rerun with source as it was BEFORE you made your changes (you
did save it didn't you?): if you still get the problem then it is not
unlikely that there is some other change you didn't know about - time to
hurt somebody <grin> - if that works OK though, you need to look very
carefully at your changes: did you change a field offset, a default, nullify
an assumption made elsewhere in the code? I'm a great fan of applying
changes in bits: add a stub routine that does nothing, test it; make form
changes to one control at a time, test it; etc. At the point it breaks you
have narrowed the damage to some very specific area.
A
 
Hard to guess what you did but clearly you changed more than you thought you
did. First, rerun with source as it was BEFORE you made your changes (you
did save it didn't you?): if you still get the problem then it is not
unlikely that there is some other change you didn't know about - time to
hurt somebody <grin> - if that works OK though, you need to look very
carefully at your changes: did you change a field offset, a default, nullify
an assumption made elsewhere in the code? I'm a great fan of applying
changes in bits: add a stub routine that does nothing, test it; make form
changes to one control at a time, test it; etc. At the point it breaks you
have narrowed the damage to some very specific area.
A








- Mostra testo tra virgolette -
Click to expand...

Thank you, Alan, for your help. I managed to solve the problem by
creating a new solution with new projects in it, copying last versions
of source files in the projects directories and compiling the
solution. This make me think the problem was related to an assembly
corruption more than to a heap damage. Now I'm able to debug my
application and to have changes to the code applied. I hope the
problem won't resurface in the future.
 
Back
Top