Complete
over 4 years ago

WERETECH-6805

This was addressed in CIQ 3.1.1.

How to debug an unhandled exception

On a fresh Eclipse install on macOS High Sierra with recommended settings (several example apps do build and run), I can't seem to get a strack trace after an unhandled exception (aka app crash). Without that information, it's pretty much impossible to debug an app, so I guess I just missed some setting.

What did I miss?
Former Member
Former Member
Parents
  • over 6 years ago
    Yes, with the catch block -- combined with e.printStackTrace() -- I perfectly see that foo() returns a type that cannot be converted. It just would be nice to have this exception also on console instead of the more general Unhandled Exception, that would make debugging a lot easier. Because I guess it's very complicated to add try-catch blocks on all entry points of my application, as most functions are called from system in case of events like timer, key press, etc.so there is no global entry point like the good old WinProc in Win32 anymore :)
Comment
  • over 6 years ago
    Yes, with the catch block -- combined with e.printStackTrace() -- I perfectly see that foo() returns a type that cannot be converted. It just would be nice to have this exception also on console instead of the more general Unhandled Exception, that would make debugging a lot easier. Because I guess it's very complicated to add try-catch blocks on all entry points of my application, as most functions are called from system in case of events like timer, key press, etc.so there is no global entry point like the good old WinProc in Win32 anymore :)
Children
No Data