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 / Visual Studio.NET / Debugging / April 2006

Tip: Looking for answers? Try searching our database.

Debugging and executiong doesnt fit

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
eduwushu - 11 Apr 2006 12:59 GMT
Hi there i have a problem with visual studio 2005:

I have a program which is bringing me some problems.Its a windows form
application with use of threading.
The point is that when i run the debugger it doesnt show me any error
message or exception and everything goes right, i can move the forms and
everything.
But when i select start without debugging when i start moving one of the
forms of my application a windows error message appears.When i get to te
report details it sais that the error code is 0xc0000005 ( i think it is
memory corruption)
I have also activated all the debugger mda's and when i run the debugger
everything goes fine but in execution the error message always appear when i
try to move a form, it's frustating !! and i dont know the way to detect with
the debugger what is happening.
Some ideas please???
Many thanks
Oleg Starodumov - 12 Apr 2006 12:32 GMT
> I have a program which is bringing me some problems.Its a windows form
> application with use of threading.
[quoted text clipped - 9 lines]
> try to move a form, it's frustating !! and i dont know the way to detect with
> the debugger what is happening.

Here are some possible approaches:

- Try to launch the application without debugger, then attach the debugger to it

- Register VS as the just-in-time debugger (Tools | Options | Debugging |
 Just-in-time - check "Managed" and "Native". The next time when the exception
 is raised, the debugger will be started and attached to the process, and
 you should be able to debug the problem. (When you see the just-in-time debugger
 dialog, check "Manually choose the debugging engines" and select both
 native and managed engines in the subsequent dialog).

- If none of the above helps, you can use tracing to debug this problem

Also, the problem looks like a race condition, so pay attention to proper
synchronization in your code.

Regards,
Oleg
[VC++ MVP http://www.debuginfo.com/]

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.