Community
Participate
Working Groups
Build Identifier: This bug is a follow up on this blog post: http://blog.objectteams.org/2010/02/why-im-sometimes-a-bad-bug-reporter/ Basically, when a user encounters a bug, they are in the middle of something and don't have the time or nerve to care what it going on. Only later, after their task is done, they want to return but then, they'll have forgotten a lot of the important details leading to incomplete and useless bug reports. So I propose a new plug-in which has these features: 1. It adds a action to the UI which reads "Save Bug". 2. When the action is invoked, the plug-in should dump the Java heap to disk along with a screen shot and a short description from the user (what they were doing at that time). 3. There should be another action which allows to load such a dump later for analysis. Using the standard debug infrastructure, it should be possible to isolate stack traces, object states and other useful information, compile them into a "bug report archive" which can then be posted on the Eclipse bug tracker to sent to someone willing to work on a bug. Reproducible: Always
Version -> 4.0 since that probably isn't going to make it into 3.6 :-)
Hello, do we have any news? I agree this kind of plug-in would be quite interesting
It is a valid enhancement request but nobody is working on it. Contributions welcome. The closest thing we have now is the "Configuration" section under Help > About > Installation Details. This provides a very detailed report of the system configuration that would be suitable to attach to a bug report. Java stack traces are rarely useful because you are typically reporting the problem after the fact when the stack isn't at the state where the error occurred. Stack dumps are mainly useful for deadlocks or infinite loops where you can capture the state while the bug is occurring. Typically this needs to happen at the VM level because at this point the UI is not responsive.
(In reply to comment #3) > Typically this > needs to happen at the VM level because at this point the UI is not > responsive. But Eclipse is started from a small exe which is independent. So this could be a watchdog that creates a stack dump when the UI thread isn't responding to a small test message within, say, 5s. When Eclipse starts again, the plugin could then offer to include this thread dump in the bug report.
