Menu

#174 "Config options" may not be empty

Next release
closed-fixed
None
3
2015-03-21
2015-03-09
No

There seems to be a regression bug in:

GNU ARM C/C++ OpenOCD Debugging 3.1.1.201502281154 ilg.gnuarmeclipse.debug.gdbjtag.openocd.feature.group Liviu Ionescu

In my setting openocd executable is launched outside of Eclipse and I always unmark "Start OpenOCD locally" option. In versions 2.xx it worked fine. Now I have to put some dummy value into "Config options", otherwise debugging will not start with the message:

Fill-in the 'Config options:' field in the Debugger tab

Thank you for your time looking into the issue

Discussion

  • Liviu Ionescu (ilg)

    • status: open --> open-accepted
    • assigned_to: Liviu Ionescu (ilg)
     
  • Liviu Ionescu (ilg)

    please check the new beta from updates-test.

     
  • Liviu Ionescu (ilg)

    btw, I have a question, why don't you start openocd automatically, do you really run it on a remote machine?

     
  • Roman Saveljev

    Roman Saveljev - 2015-03-16

    Hi,

    Thank you for looking into the problem. We have to launch OpenOCD outside Eclipse, because we embedded it into Docker container. I will try to re-test with test-update version soon.

    Best regards,
    Roman

     
  • Liviu Ionescu (ilg)

    we embedded it into Docker container.

    I have no experience with the Docker container.

    but generally if you do not run the GDB server on a remote machine, not starting it automatically is just a bad idea, which disables many of the plug-in extra functionality.

     
  • Liviu Ionescu (ilg)

    • status: open-accepted --> closed-fixed
     
  • Liviu Ionescu (ilg)

    fixed since 2.7.1-201503211846