Community
Participate
Working Groups
We should have some sort of diagnostic mode that SubMonitor can be put into which will log a stack trace whenever it is used incorrectly. The sort of errors we can detect are: 1. Attempt to report progress before any ticks are allocated (via beginTask or setWorkRemaining) 2. Attempt to invoke beginTask more than once 3. Attempt to report progress on a monitor after invoking done() 4. Attempt to report more progress than there were ticks allocated on the monitor 5. Attempt to report 0 ticks We should optionally log these so that such errors can be fixed.
Also, we should revert the fix to bug 252446 since it covers up bugs of type 1.
New Gerrit change created: https://git.eclipse.org/r/60285
+1. I suggest to use the tracing facilities of Eclipse to activate them.
New Gerrit change created: https://git.eclipse.org/r/71196
Gerrit change https://git.eclipse.org/r/71196 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?id=8e84db691394e6ecf6fd8ddacbdb5bca6df551d3
Gerrit change https://git.eclipse.org/r/60285 was merged to [master]. Commit: http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/commit/?id=cbfe3daa3a92b858cc0def6d7c94ce127411142a
Stefan, please add this to our N&N M7.
(In reply to Lars Vogel from comment #7) > Stefan, please add this to our N&N M7. Not done, took me a longer time to refind this bug. I suggest we add this as N&N to our current release.
New Gerrit change created: https://git.eclipse.org/r/148221
Gerrit change https://git.eclipse.org/r/148221 was merged to [master]. Commit: http://git.eclipse.org/c/www.eclipse.org/eclipse/news.git/commit/?id=f50202f0a1e6882c929f0e9d927b9b4f0562150d