Community
Participate
Working Groups
Created attachment 282673 [details] Screenshot of the internal error, "Problem Occurred". Current UI design as of May 2, 2020. This is a feature request. This is not related to the error I keep getting whenever Eclipse is debugging my Java application, where it is reporting about "Index out of bounds". ==================================== Currently, as of May 2, 2020 per the attachment description, the look and feel of the "Problem Occurred" dialog with the "Details" pane expanded is okayish at best, vague at worst when it comes to tracking down internal errors. Whenever I see the "Problem Occurred" and it reports about an Eclipse internal error, you always see the "localized error message" in the "Details" pane. That is fine and dandy, but what it could've been improved upon is the fact the message is "localized", and there is not enough details to track down "why" this problem existed. I proposed that whenever an Eclipse internal error occurs, whenever the user attempts to view the Details of the error, it should specifically display both: - Localized error message - Full Stack Trace of the issue. - Possibly have the messages be formatted beautifully (with paragraph breaks, etc.) for the user to easily report back, and have the developers view what went wrong at a glance. Please give this issue a consideration, even if it's just a little, so that it is easier to report internal errors that end users will face upon when Eclipse IDE alerts them, just like me. Thank you and have a good weekend.
Oh, uh, there's a typo. The sentence: "That is fine and dandy, but what it could've been improved upon is the fact the message is "localized", and there is not enough details to track down "why" this problem existed." Should have been "That is fine and dandy, but what it could've been improved upon is the fact the message is "localized", and there is not enough details to track down "where" this problem existed."
