c# - Handling rude application aborts in .NET -
I know that by asking this I am opening myself for royal ignition, but I thought I would see that Is there anyone near the stack overflow that I have a solution to a problem ...
I have a C # application which is failing on a client site so that I can reproduce locally I'm unable. Unfortunately, to get any information for me, it is very difficult (impossible) that helps in separating the source of the problem.
I have a very large error monitoring frame that is not looking for exceptions in all the normal places:
- The backstop exception handler controls in the threads < / Li>
- Application for WinForms exceptions. Thread Exception
- AppDomain.CurrentDomain.UnhandledException
that logs detailed information on the place where I have access to them.
It has been very useful in identifying problems in the production code in the past, but it is not giving me any information about the current series of issues.
My best estimate is that the main issue is one of the "rude" exception types (thread eliminated, out of memory, overflow, access violation, etc.)) which are moving from an unsurpassed shutdown Those are speeding up the process before I get an opportunity to see what is happening.
Does anyone know what I can do for snapshot info because my process is crashing that would be useful? Ideally, I would be able to write my custom log format, but if I can be a reliable way of ensuring that the crash dump is written somewhere then I would be happy.
I was hoping that I can apply the CriticalFilIZir object to the class and this one logs out the last chance error, when it has to be settled, but it does not seem to trigger in the stack overflow scenario. Had tested.
I'm unable to use Windows Error Reporting and friends due to a lack of code signing certificate.
I'm not trying to "recover" with arbitrary exceptions, I'm just trying to make a note what went wrong on the way.
Any thoughts?
You can try to create a file, it's a C ++ API, but a small It is possible to write a ++ program, which handles the process of launching your application, waits at the process handle, and then uses the process handle to create a minidump when the application dies. / P>
Comments
Post a Comment