Acknowledged

Provide more detail on ERA crash reports

I would like to see ERA crash reports provide more detail for "Unhandled Exception" and "System Error" cases.  I have quite a few instances where these occur but just this + the backtrace is not enough to determine the cause of the crash or error.

  • When you see something in ERA, it's just a friendly way to see the ciq_log files from user's devices, with the pc values translated to files/line numbers using the debug info in the iq file.  That's all the known info.

    If you use your imagination, you might conceive of an implementation where the requested additional information is also added to the ciq_log files from users' devices.

    It's not really helpful to answer every feature request with "things are the way they are because that's the way they are." With that attitude, nothing in the world would ever change or improve.

  • Both System error and unhandled exception need to be more specific.   For unhandled exception, which exception.  If a specific argument to a function call caused the error, which argument number would be helpful.  For system error, this has always been too vague.  I would like to know if it caused a crash or not, and the nature of the error.

  • What additional detail would you want to see? I'm happy to file a feature request, but I'd need more specifics about what you actually need.

  • When you see something in ERA, it's just a friendly way to see the ciq_log files from user's devices, with the pc values translated to files/line numbers using the debug info in the iq file.  That's all the known info.