Re: crash in release build

Hi,
If you don't have any idea where it's crashing (like the call stack),
you might want to consider implementing a centralized unhandled
exception handler.

// Add the event handler for handling UI thread exceptions to the
event.
System.Windows.Forms.Application.ThreadException += new
ThreadExceptionEventHandler(Application_ThreadException);
// Set the unhandled exception mode to force all Windows Forms errors
to go through our handler.
System.Windows.Forms.Application.SetUnhandledExceptionMode(UnhandledExceptionMode.CatchException);
// Add the event handler for handling non-UI thread exceptions to the
event.
AppDomain.CurrentDomain.UnhandledException += new
UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);

Then in the exception handlers, you can get the stack, for example:

private static void Application_ThreadException(object sender,
ThreadExceptionEventArgs e)
{
// e.Exception.StackTrace will contain the call stack where
the exception occurred, write it to a file or something....
...
}

If that's not helping very much, you could try to use a tool like
ADPlus to grab a crash dump of the process and use Windbg with the SOS
extension to look at the state of the program at the time of the
crash. That's more work though.

Hope that helps,
John

On Feb 7, 7:19 am, bjor...@xxxxxxxxx wrote:
The application i build in C#.net is crashing once a month. I can't
reproduce the crash.

Is there a way to track down where the program crashes, without
putting logging everywhere in the code? Is there a way to get a stack
trace of the crashing program (by the way, i'm new to C#.net, i have
experience in (unmanaged) C++).

Thanks in advance.


.

Relevant Pages

  • Re: Exception Handling...
    ... >>The try key word results in the current stack frame base, ... > private data on top of the Exception Registration... ... is the address of the exception handler. ... >>Immediately following this jump, there is inserted a jump to ...
    (comp.lang.pascal.delphi.misc)
  • Re: Exception management question...
    ... I suspect Form.Load is the result of receiving the WM_CREATE Win32 windows ... the exception in the Form Load event causes the ... they end up being handled by the Application.ThreadException event handler ... rather than the intended exception handler on the other form. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: ada compiler?
    ... high that the exception handler itself will overflow the stack (e.g. ... Storage_Error (without any further operations in the handler) would fail the ...
    (comp.lang.ada)
  • Re: VB6 How to find calling routine
    ... it means once a handler has captured ... an exception, most of the original stack context has gone because the stack ... to track all the calling routines is just too much work for too little ...
    (comp.lang.basic.visual.misc)
  • Re: Implementing Exception Handling in a VM
    ... but it basically involves walking up the call stack. ... If you don't need the debugger ... IMO a pre-search for an exception handler is required only, ...
    (comp.compilers)
Loading