windows 5.4 2016q3 arm-none-eabi-gdb.exe fails when launching from eclipse

[Brian]

gdb release:5.4 2016q3
binary package
Host:Windows 7
Eclipse Luna CDT 8.6.0
OpenOCD 0.10.0

I am setting up OpenOCD and gdb hardware debugging with my STM32F4 Discovery board (STLink debugger).
I just updated the compiler to the 5.4 2016q3 version. When I use the arm-none-eabi-gdb.exe provided I get the following error.

Error in final launch sequence
  Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run. Try "help target".
  Don't know how to run. Try "help target".

If I force the debug session to launch an older version (4.9 2015q1) it works fine.
Are there any new command line options in the latest gdb???

Also, I tried the new gdb from eclipse with an OpenOCD session i started externally and it worked!
Seems the only difference is that openOCD was opened outside eclipse.

Thanks in advance,

Brian

[Liviu Ionescu (ilg)]

to use the new gdb you need a newer version of Eclipse, Luna does not support gdb 7.10. Mars.2 should be fine, preferably Neon.

instructions to install all these tools are available at http://gnuarmeclipse.github.io.

[Brian (bmoney)]

Thanks for the reply.

I found a Eclipse Mars based toolchain from:
http://www.openstm32.org/System+Workbench+for+STM32

They don't seem to use the official gunarm release, but seems to generate
fine code and runs on the board. Don't have to manually setup debugger.
Good to know.

I did notice on the newer version of the gdb with the externally launched
OpenOCD server that debugging was faster when starting a connection and
stepping through code.

Thanks,

Brian