DEPRECATED > GNU ARM Eclipse / Bugs / #87 IllegalStateException: RequestMonitor ... done() method called more than once

Liviu Ionescu (ilg) - 2014-02-19

status: open --> open-accepted

assigned_to: Liviu Ionescu (ilg)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-02-19

hmmm... this looks very strange, I'm using it on OS X without any problems.

could you try the latest beta from

http://gnuarmeclipse.sourceforge.net/updates-test

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Eliot Stock - 2014-02-19

Tried that and got the same error:

!SESSION 2014-02-19 08:42:37.782 -----------------------------------------------
eclipse.buildId=4.3.0.M20130911-1000
java.version=1.7.0_45
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.java.product

!ENTRY org.eclipse.core.net 1 0 2014-02-19 08:42:42.235
!MESSAGE System property http.nonProxyHosts has been set to local|.local|169.254/16|.169.254/16 by an external source. This value will be overwritten using the values from the preferences

!ENTRY org.eclipse.ui.navigator 2 0 2014-02-19 08:42:43.514
!MESSAGE Can't find Navigator Content Descriptor with id: org.eclipse.jst.servlet.ui.EnhancedJavaRendering

!ENTRY org.eclipse.cdt.dsf 4 -1 2014-02-19 08:42:58.977
!MESSAGE Uncaught exception in DSF executor thread
!STACK 0
java.lang.IllegalStateException: RequestMonitor: Sequence "Configuring GDB", result for executing step #20 = Status ERROR: org.eclipse.cdt.dsf code=10005 Error executing step execute method: stepLoadImage java.lang.reflect.InvocationTargetException, done() method called more than once
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.done(RequestMonitor.java:285)
at org.eclipse.cdt.dsf.concurrent.ReflectionSequence$ReflectionStep.execute(ReflectionSequence.java:158)
at org.eclipse.cdt.dsf.concurrent.Sequence.executeStep(Sequence.java:459)
at org.eclipse.cdt.dsf.concurrent.Sequence.access$2(Sequence.java:373)
at org.eclipse.cdt.dsf.concurrent.Sequence$2.handleSuccess(Sequence.java:420)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.handleCompleted(RequestMonitor.java:376)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor$2.run(RequestMonitor.java:303)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

!ENTRY ilg.gnuarmeclipse.debug.gdbjtag.jlink 4 5012 2014-02-19 08:42:59.003
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Error executing step execute method: stepLoadImage
at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:115)
at ilg.gnuarmeclipse.debug.gdbjtag.jlink.LaunchConfigurationDelegate.launchDebugSession(LaunchConfigurationDelegate.java:278)
at ilg.gnuarmeclipse.debug.gdbjtag.jlink.LaunchConfigurationDelegate.launchDebugger(LaunchConfigurationDelegate.java:86)
at ilg.gnuarmeclipse.debug.gdbjtag.jlink.LaunchConfigurationDelegate.launch(LaunchConfigurationDelegate.java:73)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.cdt.dsf.concurrent.ReflectionSequence$ReflectionStep.execute(ReflectionSequence.java:155)
at org.eclipse.cdt.dsf.concurrent.Sequence.executeStep(Sequence.java:459)
at org.eclipse.cdt.dsf.concurrent.Sequence.access$2(Sequence.java:373)
at org.eclipse.cdt.dsf.concurrent.Sequence$2.handleSuccess(Sequence.java:420)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.handleCompleted(RequestMonitor.java:376)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor$2.run(RequestMonitor.java:303)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.IllegalStateException: RequestMonitor: Sequence "Configuring GDB", result for executing step #20 = Status OK: unknown code=0 OK null, done() method called more than once
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.done(RequestMonitor.java:285)
at ilg.gnuarmeclipse.debug.gdbjtag.jlink.FinalLaunchSequence.stepLoadImage(FinalLaunchSequence.java:658)
... 17 more
!SUBENTRY 1 org.eclipse.cdt.dsf 4 10005 2014-02-19 08:42:59.004
!MESSAGE Error executing step execute method: stepLoadImage
!STACK 0
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.cdt.dsf.concurrent.ReflectionSequence$ReflectionStep.execute(ReflectionSequence.java:155)
at org.eclipse.cdt.dsf.concurrent.Sequence.executeStep(Sequence.java:459)
at org.eclipse.cdt.dsf.concurrent.Sequence.access$2(Sequence.java:373)
at org.eclipse.cdt.dsf.concurrent.Sequence$2.handleSuccess(Sequence.java:420)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.handleCompleted(RequestMonitor.java:376)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor$2.run(RequestMonitor.java:303)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.IllegalStateException: RequestMonitor: Sequence "Configuring GDB", result for executing step #20 = Status OK: unknown code=0 OK null, done() method called more than once
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.done(RequestMonitor.java:285)
at ilg.gnuarmeclipse.debug.gdbjtag.jlink.FinalLaunchSequence.stepLoadImage(FinalLaunchSequence.java:658)
... 17 more
Root exception:
java.lang.IllegalStateException: RequestMonitor: Sequence "Configuring GDB", result for executing step #20 = Status OK: unknown code=0 OK null, done() method called more than once
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.done(RequestMonitor.java:285)
at ilg.gnuarmeclipse.debug.gdbjtag.jlink.FinalLaunchSequence.stepLoadImage(FinalLaunchSequence.java:658)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.cdt.dsf.concurrent.ReflectionSequence$ReflectionStep.execute(ReflectionSequence.java:155)
at org.eclipse.cdt.dsf.concurrent.Sequence.executeStep(Sequence.java:459)
at org.eclipse.cdt.dsf.concurrent.Sequence.access$2(Sequence.java:373)
at org.eclipse.cdt.dsf.concurrent.Sequence$2.handleSuccess(Sequence.java:420)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.handleCompleted(RequestMonitor.java:376)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor$2.run(RequestMonitor.java:303)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-02-19

could you try to let the plug-in start the server automatically, with the correct configuration, and let me know the result?

the gdb server must be started with many options on the command line, and that's the purpose of the plug-in, to send them as expected.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Eliot Stock - 2014-02-19

Sure. That gives me this error on the UI:

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:2331

Error message from debugger back end:
Protocol error: qXfer:features:read (target-features) conflicting enabled responses.
Protocol error: qXfer:features:read (target-features) conflicting enabled responses.

The server is starting up OK:

SEGGER J-Link GDB Server V4.80dSEGGER J-Link GDB Server V4.80d Command Line Version

JLinkARM.dll V4.80d (DLL compiled Jan 29 2014 14:28:37)

-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: yes
Generate logfile: off
Verify download: on
Init regs on start: on
Silent mode: off
Single run mode: off
------J-Link related settings------
J-Link script: none
Target interface: SWD
Host interface: unknown
Target endian: little
Target interface speed: 1kHz

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link ARM V8 compiled Nov 25 2013 19:20:08
Hardware: V8.00
S/N: 268006243
OEM: SEGGER-EDU
Feature(s): FlashBP, GDB
Checking target voltage...
Target voltage: 1.90 V
Listening on TCP/IP port 2331
Connecting to target...Connecting to target...Connected to target
Waiting for GDB connection...Waiting for GDB connection...Connected to 127.0.0.1
GDB closed TCP/IP connection

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-02-19

I'm not sure, but V4.80d might have some problems, I'm using 4.80e.

to diagnose this, I suggest you start with the latest SEGGER software and the latest plug-ins from updates-test, with a new workspace, a newly generated sample using the templates and a new debug configuration. please read the updated documentation pages for details.

if you still cannot connect, I need more details about your configuration, to see what differs from my configuration.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Eliot Stock - 2014-02-19

Moving to 4.80e and using the updates-test for both plugins hasn't made any difference. Still seeing the same error. Will have to try with a new workspace, project and debug config tonight.

In the meantime I need to get working again. Any idea why I can't rollback to my last known good installation of Eclipse? I'm getting these errors:

An error occurred while collecting items to be installed
session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,ilg.gnuarmeclipse.debug.gdbjtag.jlink,1.2.1.201401111229
No repository found containing: org.eclipse.update.feature,ilg.gnuarmeclipse.debug.gdbjtag.jlink,1.2.1.201401111229
No repository found containing: osgi.bundle,ilg.gnuarmeclipse.managedbuild.cross,1.7.1.201401111229
No repository found containing: org.eclipse.update.feature,ilg.gnuarmeclipse.managedbuild.cross,1.7.1.201401111229

Do you keep the old versions around on your update site?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Liviu Ionescu (ilg) - 2014-02-19
  
  sorry for the inconveniences, but if you do not help me reproduce your problem, I cannot find a solution.
  
  rolling back is tricky. I guess it is easier to unzip a new Eclipse and start from scratch.
  
  in SourceForge are archived all releases, but I would not use any previous versions.
  
  the latest version should work, I tried it with all sizes of J-Link probes and various boards.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Eliot Stock - 2014-02-20

Have done my best to start from scratch with a new workspace, project and debug config, but since I don't use the GNU ARM Eclipse plugin for building my project, flashing my device, and running the GDB server, there's not really much point and I haven't got far with it. I only use the plugins for editing code and running the GDB client. I have existing Makefiles for building and flashing.

So although rolling back may be tricky, it seems to be my only option. The debug configuration was working in the versions I listed above.

How do I find these versions on the SF server? They're not listed in your artifacts.xml or content.xml files in the root of the 'updates' repository.

osgi.bundle,ilg.gnuarmeclipse.debug.gdbjtag.jlink,1.2.1.201401111229
org.eclipse.update.feature,ilg.gnuarmeclipse.debug.gdbjtag.jlink,1.2.1.201401111229
osgi.bundle,ilg.gnuarmeclipse.managedbuild.cross,1.7.1.201401111229
osgi.bundle,ilg.gnuarmeclipse.managedbuild.cross,1.7.1.201401111229

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Liviu Ionescu (ilg) - 2014-02-20
  
  all archives are in the Files section.
  
  without enough info to reproduce, this issue will be closed.
  
  good luck!
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-03-17

status: open-accepted --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

IllegalStateException: RequestMonitor ... done() method called more than once

A family of Eclipse CDT extensions and tools for GNU ARM development.

Group

Searches

Help

#87 IllegalStateException: RequestMonitor ... done() method called more than once

Discussion