Ctrlflow Blog

Categories


Recent Posts


Frequent Issues When Setting Up Automated Error Reporting for Eclipse-based Products

CtrlflowCtrlflow

Why does Automated Error Reporting Not Show Up in My Eclipse Runtime Workbench?

When launching your Eclipse product from your Eclipse IDE via a launch configuration, make sure that your launch configuration contains the line “-Declipse.buildId” in your launch configuration’s VM arguments section. Otherwise the error reporting client will disable itself immediately on startup because it thinks it got activated during a JUnit test suite execution.

aer-launch-config

Why does Automated Error Reporting Not Show Up in My Eclipse Product ?

Likely because your product does not declare an eclipse.buildId system property. On startup the client checks whether the product it is running in declares an system property named eclipse.buildId. If it cannot find this system property, it simply disables itself for the same reason as above.

Please check that your product configuration actually specifies a product version.

It was reported that when building with some Maven Tycho versions, the product may set a system property “build.id” instead of “eclipse.buildId”. To force Tycho use eclipse.buildId in addition, add the following line to your .product file:


<configuration>
    <property name="eclipse.buildId" 
              value="${unqualifiedVersion}.${buildQualifier}"> 
    </property>
</configuration>

Why does my stack trace sometimes contain “HIDDEN.HIDDEN” instead of the actual class name?

Reporters can decide whether they want to anonymize stack traces or not. If enabled, all classes that do not belong your application are replaced by HIDDEN.HIDDEN. By default all package prefixes you specified in your project settings will be transmitted as-is. If have additional 3rd-party dependencies (like org.eclipse) you’d like to remain unanonymized, you can ask the clients to not-anonymize them by adding them to the non-anonymizable packages list:

aer-settings-unanonymizable

How can I enable debug output in my Eclipse runtime workbench?

Although the setup is rather easy, sometime things will just not work as expected. Then the debug output can help to spot and fix the problem quickly. To enable debug output for your runtime workbench, open your product launch configuration, go to the tracing tab, select org.eclipse.epp.logging.aeri.core from the list and check the debug option:

aer-plugin-traceing

To see the additional output, make sure you have opened the Eclipse Error Log View or launched your Eclipse product with the -consoleLog program argument (specified on the Arguments tab, in the Program Arguments text field).

How do I enable Debug Output In My Eclipse (IDE-based) Product At Runtime?

Configuring Eclipse’ tracing options in your products can be a pain. Thus, you can enable the additional debug output in your product at runtime via the Error Reporting preference page. This has the same effect as setting the tracing option but can be used easily by you to test your product and by your users to get additional debug information.

aer-debug-error-reporting-preference

Ctrlflow Automated Error Reporting

Learn more about all features