Program crashes not trapped by debugger.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a VB .NET application that even when we execute it in debug mode from within the Visual Studio IDE, it will crash and the debugger will not trap the error. This makes it nearly impossible to isolate the error condition. The crash happens at seemingly random times and sometimes even when the application is just sitting there with no user interaction.

We are interested in any ideas anyone has on how to trap this error. Are there any third party debuggers to try? Are there some extra MicroSoft tools to facilitate the resolution of this problem?

Any input is greatly appreciated.
 
canhamdlc said:
We have a VB .NET application that even when we execute it in debug mode
Click to expand...
from within the Visual Studio IDE, it will crash and the debugger will not
trap the error. This makes it nearly impossible to isolate the error
condition. The crash happens at seemingly random times and sometimes even
when the application is just sitting there with no user interaction.
We are interested in any ideas anyone has on how to trap this error. Are
Click to expand...
there any third party debuggers to try? Are there some extra MicroSoft
tools to facilitate the resolution of this problem?Turn on First chance exceptions. Then the debugger will break whenever an
exception is thrown. The default is to break only on unhandled exceptions.
This has the added benefit of breaking to the line of code where the
exception is generated so you can inspect all the local variables which will
be lost as the exception propagates up the stack.

In VisualStudio choose Debug>Exceptions> When an Exception is thrown: break
into the debugger.


David
 
from within the Visual Studio IDE, it will crash and the debugger will not
trap the error. This makes it nearly impossible to isolate the error
condition. The crash happens at seemingly random times and sometimes even
when the application is just sitting there with no user interaction.<<<

Mhm... Do you get a Windows crash error message (GPF or similar) or isn't
there any message? Or does VS.NET want to show you the disassembly? If
it's the latter case, you should check the combobox in the toolbar of VS.NET
if it's set to "Debug".
 
We have a VB .NET application that even when we execute it in debug mode from within the Visual Studio IDE, it will crash and the debugger will not trap the error. This makes it nearly impossible to isolate the error condition. The crash happens at seemingly random times and sometimes even when the application is just sitting there with no user interaction.

We are interested in any ideas anyone has on how to trap this error. Are there any third party debuggers to try? Are there some extra MicroSoft tools to facilitate the resolution of this problem?

Any input is greatly appreciated.
Click to expand...

What is the exception?
 
Where is your exception handling code?
Is there any relevant info in the Event Log viewer?

Richard
 
Back
Top