Does anybody know how to catch all exceptions in monomac?
On windows .net I wrap the run loop in a try{}catch and also use:
Application.ThreadException + AppDomain.CurrentDomain.UnhandledException
It would nice to be able to get crash reports from my new mac software I'm beta testing.
Related
I am testing a swing application, with the standalone version of Robot Framework and I am now at the point that my tests go through to the end.
However, Robot Framework will hang after the output of the report etc., leaving the prompt open.
Now i have two questions:
Is there a way that Robotframework closes this too?
And how does RF close Applications?
In our software we are using the system.exit(0)-code to terminate. This also terminate the Robotframework.
After I created a parameter in the beginning, that checked if the Software is starting with RF, it exclude the system.exit and RF ends the test with no Problems.
I want to add bugsplat reporting to my Adobe Air app, this part of the code is done and working.
However, for QA purposes I need an easy way to crash (hard crash, not only cause an exception) the application so the bugsplat window will come up.
Most of my attempts end up in Air throwing an exception, not forcing the application to close.
Any ideas?
I added a new console application project to my VS2012 solution.
When it encounters an exception, I get an error dialog, and VS2012 does not break and go to the source line that threw the exception.
The original project that was created together with the Solution does break on exceptions properly, so I think the issue is that the newly created executable is not marked as relevant for breaking on exceptions. (The debugger is "not attached"? I'm not sure if this is the right term)
How can I make VS2012 start breaking on exception in a project?
I am using the Debug configuration, the pdb is being generated.
There is an issue with recent x64 Windows systems when they do not propagate exception properly back to the x64 application when function calls cross kernel boundaries.
There are plenty of posts here on SO and all over the internet about it, for example the-case-of-the-disappearing-onload-exception-user-mode-callback-exceptions-in-x64
You can fight it to some extent by going to Debug->Exceptions and flagging CLR exceptions Thrown column. But note that then VS would break even on the exceptions handled by you.
in a closed dll, i've sometime this exception:
Is possible to catch it?
Windows mobile, netcf 3.5, C#
Thanks.
That's an access violation exception. You can try the SEHException class, but I'm not entirely sure if that's available in the compact framework.
Either way, you'll be better off fixing the issue that's causing the exception.
I am using Visual Studio 2008 Express and am writing unit tests where there are many expected unhandled exceptions. This cause numerous exception assistant popups to display when running these tests in the debugger.
I have disabled the exception assistant in the VS options, but a different unhandled exception dialog pops up instead. I know it is possible to get rid of these with Visual Studio Professional, but how do you do this with the express edition?
By the way, I am using Assert.Throws instead of the ExpectedException attribute (NUnit), which causes this, but I want to use the Assert.Throws instead. Thanks!
In the Debug menu, go to Exceptions (Ctrl+Alt+E). From here you can tell the debugger not to break when an exception is thrown. Just uncheck all the boxes for the lazy option, or go digging for the specific exceptions you don't want it to break on.
Note however, that this may not be what you want to happen under normal debugging situations, so don't forget to turn it back on later if you're trying to debug something & want to find the exception.
Edit: My apologies, even though it's written several times in the question (including the title), I failed to notice you were talking about the express edition... teach me for skim reading the question. Not sure if the above works or not in express edition, so it might still be worth a try.
Edit 2: Ok, looks like the Exceptions dialog is still available in express edition.
I'll take a guess that you're encountering one of the following:
You're throwing a "special" exception like StackOverflowException that the runtime handles differently from other exceptions.
Your test code creates a new thread, and on that thread an exception is thrown.