Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / VB.NET / March 2008

Tip: Looking for answers? Try searching our database.

Heap damage

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Monica R. - 29 Feb 2008 11:06 GMT
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!
Alan Gillott - 29 Feb 2008 12:54 GMT
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

> 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
[quoted text clipped - 7 lines]
> I never encountered a similar problem and I need help.
> Thank you!
Monica R. - 01 Mar 2008 14:18 GMT
> 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
[quoted text clipped - 21 lines]
>
> - Mostra testo tra virgolette -

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.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.