unhandled-exception

I am trying to start an error-reporting activty if unhandled exception detected. The problem is with exceptions thrown from main thread. Is there any way to start an activity if main thread crashed? The approach I've seen used for error catching in an UncaughtExcpetionHandler is to write the crash data out to file and then start the error handling Activity when the application is restarted based on the existence of the crash data file. Depending on what you want your Activity to do, this might work for you. I think this is the wrong way to go about it. What you need to do is make sure you

I have a handler for Application.ThreadException , but I'm finding that exceptions aren't always getting passed to it correctly. Specifically, if I throw an exception-with-inner-exception from a BeginInvoke callback, my ThreadException handler doesn't get the outer exception -- it only gets the inner exception. Example code: public Form1() { InitializeComponent(); Application.ThreadException += (sender, e) => MessageBox.Show(e.Exception.ToString()); } private void button1_Click(object sender, EventArgs e) { var inner = new Exception("Inner"); var outer = new Exception("Outer", inner); //throw

Is it possible to crash a regular user-mode process on Windows-7 without getting the Windows Error Reporting (WER) dialog? (When and if WER is normally enabled and no specific flags are applied.) Note: I'm not interested in disabling WER , I'm interested in crash scenarios where WER isn't launched although it should and Windows "silently" terminates an app. On Windows XP, it is pretty trivial to write a C or C++ application (in user mode) that messes up its own address space in such a way that when an Access Violation (or other unhandled Win32 Exception) is finally raised, Windows XP will just

In TPL, if an exception is thrown by a Task , that exception is captured and stored in Task.Exception , and then follows all the rules on observed exceptions . If it's never observed, it's eventually rethrown on the finalizer thread and crashes the process. Is there a way to prevent the Task from catching that exception, and just letting it propagate instead? The Task I'm interested in would already be running on the UI thread (courtesy of TaskScheduler.FromCurrentSynchronizationContext ), and I want the exception to escape so it can be handled by my existing Application.ThreadException

I'm seeing different behavior with exceptions being caught or not being caught when I am debugging vs. when I am running a compiled .exe. I have two forms (Form1 and Form2). Form1 has a button on it which instantiates and calls ShowDialog on Form2. Form2 has a button on it which intentionally produces a divide by zero error. When I'm debugging, the catch block in Form1 is hit. When I run the compiled .exe, it is NOT hit, and instead I get a message box that states, "Unhandled exception has occurred in your application. If you click continue, the application will ignore this error and attempt