Bug 322790 - [ErrorHandling] Usability: Improve Fatal Error Reporting
Summary: [ErrorHandling] Usability: Improve Fatal Error Reporting
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-16 09:55 EDT by Martin Oberhuber CLA
Modified: 2019-09-06 16:09 EDT (History)
3 users (show)

See Also:


Attachments
Sample of the current fatal error dialog (12.62 KB, image/gif)
2010-08-16 09:55 EDT, Martin Oberhuber CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2010-08-16 09:55:12 EDT
CQ:WIND00201302
Build ID: Any Eclipse 3.5.x, as well as Helios (3.6.0)

As an Eclipse end user, I am confused when a fatal error dialog refers me to "the .log file" but I don't know what or where that .log file is or what I'm supposed to do with it. I want the dialog to give me access to more information about the error, or allow me to save the errorlog in a place where I can send it to my vendor's support department. Note that in many cases, more than just the .log file will be relevant for a vendor's support department (eg Workspace state, configuration, ...)

Consider the Microsoft Fatal Error reporting mechanism for example - it provides a button where I can show the error report, and allows me to send that error report to support. Or, consider the Apple Fatal Error reporting mechanism.

I understand that when a fatal error has occurred, any additional work for providing more error reporting is at risk of further destabilizing the system. But on the other hand I believe that with a good reporting framework in place for such fatal errors, it's much likely that fatal errors can be fixed so I think that it's an important request. Perhaps the minimal request can be considered for 3.7 or even 3.6.x, with more work moving forward?

Minimal Acceptance Criteria:
----------------------------
- Show to the absolute pathname where the .log is stored

Nice to have:
-------------
- Provide a button for saving the .log in a different place
- Provide a button to open a subdialog with more information about the
  fatal error
- Provide an infrastructure for vendors to plug-in log collectors that 
  handle fatal errors (maybe out-of-process)

Implementation Info:
--------------------
The error handler seems to reside in the "org.eclipse.ui.ide" plug-in, externalized Strings for the dialog are in 
   org.eclipse.ui.internal.ide/messages.properties
and are named "InternalError*" and "FatalError" - basically any text that refers to "the .log file".
Comment 1 Martin Oberhuber CLA 2010-08-16 09:55:39 EDT
Created attachment 176674 [details]
Sample of the current fatal error dialog
Comment 2 Martin Oberhuber CLA 2010-08-16 09:57:55 EDT
Information about the Windows error reporting framework is available on the Internet ("Using WER").
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.