Re: application crash

Thanks for the reply.
I will try the AppDomain.CurrentDomain.UnhandledException. But is it work
also for WindowsForms application? my application is console+windows Forms.
Also, can you please tell me if this is enough?

AppDomain.CurrentDomain.UnhandledException += new
UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);

private static void CurrentDomain_UnhandledException(object sender,
UnhandledExceptionEventArgs e)
{
Exception ex = (Exception)e.ExceptionObject;
MessageBox.Show("Unhandled Exception");
MessageBox.Show(ex.GetType().ToString()+"\r\n"+ex.StackTrace);
}

Thanks


"Lloyd Dupont" wrote:

> The .NET Framework 2.0 don't handle the exception the same way as 1.1.
> Basically the process is more likely to terminate after an exception than in
> 1.1.
>
> All the quirk of exception handling is smoething somewhat obscure.
> Exception event method don't always work as expected, if at all.
> It's hard to find clear and complete documentation on the topic.
>
> Anyway you could always try to register an event handler on
> AppDomain.CurrentDomain.UnhandledException
>
> I think it would be too late to save the application, but at least you
> should get the information you need, I believe.
>
> "barbutz" <barbutz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:CBD91DF6-917F-4212-A2B8-843FBA5A389D@xxxxxxxxxxxxxxxx
> > Hi,
> >
> > I wrote an application that is basically http loader. It loads 1030
> > concurrent threads and start to send http requests to a web server.
> > The problem is that sometimes when i get in the morning to check the
> > results, the application is not running!! There is no alert and no crash
> > notification whatsoever!
> > Maybe i have a bug in my code but if my application crash there should be
> > some error message by .net framework or unhandled execption. I'm very
> > frustrated and i tried everything to catch every exception but no luck.
> > It doesn't happens all the time and it happens when the application is
> > running for few hours.
> > I also run a performance monitor on the process and there was no memory
> > leak
> > or unusuall behaviour before the process was terminated. It's like someone
> > is
> > killing the process like from task manager.
> > My application is compiled in framework 2.0 and i have to say that in
> > former
> > versions when the application was compiled in framework 1.1 i had no such
> > problem!
> > Is there a known problem in framework 2.0? If not, please tell me what i
> > can
> > do in order to find the problem.
> >
> > Thanks!
>
>
>
.

Relevant Pages

  • Re: application crash
    ... >> All the quirk of exception handling is smoething somewhat obscure. ... >>> I wrote an application that is basically http loader. ... >>> Maybe i have a bug in my code but if my application crash there should ... >>> some error message by .net framework or unhandled execption. ...
    (microsoft.public.dotnet.framework)
  • Re: SetUnhandledExceptionFilter
    ... The only way to prevent at all cost a crash in the applicaiton ... Looking at a full dump of Word.exe and/or LotusNotes is the only way ... A bad heap metadata will cause an access violation, ... normally dismissed in some wide exception handler) ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Event ID 7031 Exchange 2003
    ... I could not find any exceptions in the crashdump file. ... It seems like the information store crash is "silent" with no other error ... What is the process that had the exception. ...
    (microsoft.public.exchange2000.information.store)
  • Re: Standby-Sleep Problem
    ... If your driver does not explicitly show up in the crash dump, then it does not mean that the crash is not your driver's fault. ... If you cannot attach a debugger, then you will not be successful in developing your driver. ... Break instruction exception - code 80000003 ...
    (microsoft.public.development.device.drivers)
  • Re: Checking for null parameter
    ... Would you say that an exception can occur in the body of printLine? ... you could have made printLength() private. ... It does not crash if *and only if* called from the mainyou show. ... If you document that it might throw an NPE, ...
    (comp.lang.java.programmer)
Loading