 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / CLR / August 2004How can I trace the loc/reason of VB.NETApp crashing w/o any excep
Question: I have a problem with tracing the reason of VB.NET Application crash without any exception. That is, it doesn't throw any handled/unhandled exception despite the fact that all the sub/functions have try-catch for system.exception and i have set the machine.config for jitdebugging to true. Is there any memory leak or illegal instruction? What could be the possible reasons? How can I debug/trace the location where the fault lies? I want to trace the line or atleast the function which is causing the crash. Any easy method to debug/trace or any tool for that purpose?? I have the following configuration: WinXP with sp1, Framework 1.0, VS.NET 2002, VB.NET and some third party controls(grids, listbars etc) + COM components(unmanaged code) Please help. Please someone reply..... Hey microsoft ppl please care to reply... > Question: I have a problem with tracing the reason of VB.NET Application crash > without any exception. That is, it doesn't throw any handled/unhandled [quoted text clipped - 9 lines] > > Please help. Did you try to use debugger, like dbgclr? Look it up on MSDN if you don't have it (included in Framework SDK) HTH Alex > Please someone reply..... > [quoted text clipped - 13 lines] > > > > Please help. > Question: I have a problem with tracing the reason of VB.NET Application > crash without any exception. In the machine.config (I think that's where it is) you can specify how you want the O/S to handle crash dumps. Enable crash dumps, then look at them using WinDebug/SoS or VS.NET.  SignatureChris Mullins In DevStudio you should be able to set the behavior of the debugger when an exception is thrown. You should set it so that all exceptions that are thrown cause the debugger to halt the execution of the program. Under the options for debugger/exceptions, select the "Common Runtime Exceptions" and set the option to break into the debugger when the exception is thrown. You should also subscribe to the appdomain.UnhandledException event to determine if some piece of code is throwing an exception you are not catching. If one of the controls is directly calling TerminateProcess or something similar then there is little you can do. > Question: I have a problem with tracing the reason of VB.NET Application crash > without any exception. That is, it doesn't throw any handled/unhandled [quoted text clipped - 9 lines] > > Please help. Free MagazinesGet 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 ...
|
Reply to this Message
|
 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.