When an exception is raised, it is printed out to standard error! (or how do I get exceptions to be printed to X or displayed in a window?
One feature of running an application in the gtk mainloop is that exceptions raised don’t cause an actual crash. All that happens is the callback that was executing will be interrupted — the mainloop goes on spinning and handling events. The exception is printed out to standard error, which is great for development and developer-testing, but not as great when running without a console attached to your application, or in a production environment. There are two approaches here, both useful in different situations. • The first is assigning your own file to sys.
Related Questions
- I get the following exception and error message: com.pheox.jcapi.JCAPIJNIRuntimeException: Exception raised in JCAPI.DLL: JCAPIKeyStore_setKeyEntry() - Could not import private key. What is wrong?
- I am not receiving data exception messages but I am receiving data exceptions. What is the best method to analyze a data exception error to determine where the error occurs?
- When an exception is raised, it is printed out to standard error! (or how do I get exceptions to be printed to X or displayed in a window?
