Community
Participate
Working Groups
Build Identifier: I20110613-1736 When opcontrol is invoked, if it returns an error, the error isn't handled in a transparent way for the user. In order to find the error message emitted by opcontrol, the user must have had the debug switch turned on for this plug-in. Additionally, the dialog message that pops up is quite misleading. If you do know that you can turn on the debug switch, instead of the output going to a conventional place in the SDK, such as the Error Log, it goes to the console, which might be hard to notice, particularly if Eclipse was started using a desktop icon. Reproducible: Always Steps to Reproduce: 1. Intentionally make an error in the Profile configuration that will cause opcontrol to emit an error message and return with a non-zero error code. 2. Notice the misleading dialog, and lack of actual output from opcontrol
Created attachment 199204 [details] Patch to improve error handling of opcontrol See additional comments in the actual patch file.
Pushed with e99ec70f8861245c752fbcca5527e3eee7d7096e. Thanks! Let us know if there are more issues.
Thanks for having a look at and committing this patch so quickly :-)
Has this been cherry-picked to stable-0.8?
(In reply to comment #4) > Has this been cherry-picked to stable-0.8? No, will do today.
(In reply to comment #5) > (In reply to comment #4) > > Has this been cherry-picked to stable-0.8? > > No, will do today. Done. Longer day than I thought ;-)
Comment on attachment 199204 [details] Patch to improve error handling of opcontrol Less than 250 lines.