uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Klügl <peter.klu...@averbis.com>
Subject Re: Ruta: Best way to debug extensions
Date Fri, 05 Feb 2016 09:38:05 GMT
Hi,

my best guess is that something blocks the SWT thread. For finding the
lock I would recommend a good profiling tool. I normally use YourKit
Profiler or VisualVM (free).

I assume that you start the Eclipse with some additional plugins for
your extension? Does Eclispe freeze also without them? You can further
investigate their status in the osgi console with other commands:
http://www.eclipse.org/equinox/documents/quickstart-framework.php

Best,

Peter

Am 02.02.2016 um 18:28 schrieb Miguel Alvarez:
> Thanks Peter!
>
> I did that and I am attaching the log to this email...
> I don't have any extensions with the INSTALL status. The debug instance of
> Eclipse starts up fine, but as soon as I modify any files in it, I get the
> following error (see below) and everything freezes. I am not sure you will
> be able to help me with this, but just in case.
>
> Thanks!
> Miguel
>
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-02-02 09:22:31.033
> !MESSAGE Unable to create class
> 'org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor' from bundle
> '474'
>
> !ENTRY org.eclipse.equinox.event 4 0 2016-02-02 09:22:31.718
> !MESSAGE Exception while dispatching event org.osgi.service.event.Event
> [topic=org/eclipse/e4/ui/model/ui/ElementContainer/selectedElement/SET] to
> handler org.eclipse.e4.ui.services.internal.events.UIEventHandler@2e7cd276
>
> !ENTRY org.eclipse.ui 4 0 2016-02-02 09:22:33.374
> !MESSAGE Unhandled event loop exception
> Error while logging event loop exception:
>
> !ENTRY org.eclipse.ui 4 0 2016-02-02 09:22:34.281
> !MESSAGE Unhandled event loop exception
> Error while logging event loop exception:
> Exception in thread "Worker-4"
>
> -----Original Message-----
> From: Peter Klügl [mailto:peter.kluegl@averbis.com] 
> Sent: January 27, 2016 1:10
> To: dev@uima.apache.org
> Subject: Re: Ruta: Best way to debug extensions
>
> Hi Miguel,
>
> I use the Ruta Workbench started in debug mode from within another eclispe
> all the time, but I never observed this - meaning this should work. This is
> also how I debug the workbench extensions. There is also an option to run
> scripts in the same vm in order to debug the execution of rules in the
> original eclipse.
>
> Is there no error at all in the error log or in the log of eclipse or in the
> console of the original eclipse?
> When does Eclipse terminate? When a launch configuration is executed or when
> the plugins are loaded (e.g., rule editor)?
> Does the rule editor work correctly?
> Are the plugin loaded correctly?
>
> You can start the second eclipse with an ogsi console in order to validate
> the status of the bundles. My program arguments are normally:
>
> -os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl}
> -consoleLog -clean -console
>
> Then, you can type "ss" in the console of the original eclipse in order to
> display the status of the bundles of the launched eclipse. Can you check the
> status of the ruta bundles and of your extension ("INSTALLED"
> is normally bad, "ACTIVE" is good).
>
> Best,
>
> Peter
>
> Am 27.01.2016 um 08:15 schrieb Miguel Alvarez:
>> Hi Peter,
>>
>>  
>>
>> What is the easiest way to debug RUTA Extensions? I tried searching in 
>> the mailing list for some information about this, but I could find much.
>>
>> I have tried running the extension project as an Eclipse Application, 
>> but as soon as I start modifying/running any RUTA scripts (within the 
>> debug
>> session) in order to debug the extensions, it terminates unexpectedly 
>> all the times (it hangs without giving much of an error).
>>
>>  
>>
>> These are the settings for the launch configuration I am using:
>>
>>  
>>
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>
>> <launchConfiguration type="org.eclipse.pde.ui.RuntimeWorkbench">
>>
>> <booleanAttribute key="append.args" value="true"/>
>>
>> <booleanAttribute key="askclear" value="true"/>
>>
>> <booleanAttribute key="automaticAdd" value="true"/>
>>
>> <booleanAttribute key="automaticValidate" value="false"/>
>>
>> <stringAttribute key="bootstrap" value=""/>
>>
>> <stringAttribute key="checked" value="[NONE]"/>
>>
>> <booleanAttribute key="clearConfig" value="false"/>
>>
>> <booleanAttribute key="clearws" value="false"/>
>>
>> <booleanAttribute key="clearwslog" value="false"/>
>>
>> <stringAttribute key="configLocation"
>> value="${workspace_loc}/.metadata/.plugins/org.eclipse.pde.core/Eclips
>> e
>> Application"/>
>>
>> <booleanAttribute key="default" value="true"/>
>>
>> <booleanAttribute key="includeOptional" value="true"/>
>>
>> <stringAttribute key="location"
>> value="${workspace_loc}/../runtime-EclipseApplication"/>
>>
>> <stringAttribute key="org.eclipse.jdt.launching.JRE_CONTAINER"
>> value="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.interna
>> l.debu g.ui.launcher.StandardVMType/JavaSE-1.7"/>
>>
>> <stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS"
>> value="-os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl 
>> ${target.nl} -consoleLog"/>
>>
>> <stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER"
>> value="org.eclipse.pde.ui.workbenchClasspathProvider"/>
>>
>> <stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS"
>> value="-Dosgi.requiredJavaVersion=1.7 -Xms40m -Xmx2048m"/>
>>
>> <booleanAttribute key="pde.generated.config" value="false"/>
>>
>> <stringAttribute key="pde.version" value="3.3"/>
>>
>> <stringAttribute key="product" value="org.eclipse.platform.ide"/>
>>
>> <booleanAttribute key="show_selected_only" value="false"/>
>>
>> <booleanAttribute key="tracing" value="false"/>
>>
>> <booleanAttribute key="useCustomFeatures" value="false"/>
>>
>> <booleanAttribute key="useDefaultConfig" value="true"/>
>>
>> <booleanAttribute key="useDefaultConfigArea" value="true"/>
>>
>> <booleanAttribute key="useProduct" value="true"/>
>>
>> <booleanAttribute key="usefeatures" value="false"/>
>>
>> </launchConfiguration>
>>
>>  
>>
>> Any help with this would be much appreciated.
>>
>>  
>>
>> Thanks,
>>
>> Miguel
>>
>>


Mime
View raw message