Description Frikkie Thirion 2010-12-26 15:45:29 EST

Build Identifier: 20100917-0705

(Test preformed with CDT_master I201009241320 and I201010271448)

In order to disable and enable the interrupts on the ARM Cortex-M3 while debugging, specific commands can be send to the OpenOCD JTAG interface, namely:
"cortex_m3 maskisr off" and "cortex_m3 maskisr on"

To accomplish this, GDB needs to send these commands to OpenOCD when program execution is halted (Ctrl-C), single stepped (step and next) and resumed (continue)

The following GDB command file accomplishes this
# -- Start --
define hook-continue
mon cortex_m3 maskisr off
end

define hook-stop
mon cortex_m3 maskisr on
end

define hook-step
mon cortex_m3 maskisr on
end

define hook-next
mon cortex_m3 maskisr on
end
# -- End --

When using this command file with a GDB debug session directly in the text user interface (gdbtui), all the hooks are exercised.

When launching the debug session via the GDB Hardware Debugging Plug-in, all the hooks are exercised, except for 'hook-continue' (Resume)

-->Is there a reason why Eclipse won't allow 'hook-continue' to be registered in GDB?

The program debugging can't be accomplished without interrupts being reenabled upon resuming of the program, making this a major problem

Reproducible: Always

Steps to Reproduce:
1.Create a debug command file 'gdbCommands', containing the hook-XXXs defined above.
2.In the Debug configurations, create a GDB Hardware Debugging configuration, specifying the GDB command in the Debugger tab: <path to gdb>/arm-none-eabi-gdb --command=gdbCommands
3.Launch the debug session
(Note: An ARM development kit, hardware JTAG and OpenOCD will probably be required to reproduce the bug)