-
-
Notifications
You must be signed in to change notification settings - Fork 132
Description
Description
Normally the reset button works as expected. However, for one debug configuration that I set up it does not. This is a debug configuration with Initial reset and Pre-run/restart disabled as well as Load executable disabled. With this configuration I can start Eclipse/gdb/openocd with a running target connected without affecting the target. This much seems to work fine. However, after some normal debugging, if I try to reset the target using the reset toolbar button, the target just halts for a very short time and then continues running. This is verified by looking at the packets received by openocd when running with -d3 logging option.
[Description of the bug or feature]
The behavior of the reset button with my debug configuration is:
Halt
Continue <--- if configured to continue
Expected behavior:
The preferred behavior of the reset button with my debug configuration is:
Halt
Reset <--- and don't run, stay at reset vector
Set temporary breakpoint <--- if a temp breakpoint is configured
Continue. <--- if continue is configured
Note: A work-around is to enter this into the gdb console (after halting the target):
mon reset halt
tbreak boot_card <-- where I normally configure a temp bp after a reset
continue <-- run to boot_card
- [plug-in version] 4.1.1.201606210758
- [Eclipse version] Mars.2 (4.5.2)
- [Java version] openjdk version "1.8.0_102"
- [operating system] Linux 4.7.3-100.fc23.x86_64 READ ME FIRST! #1 SMP
- [toolchain version] arm-rtems4.12-gcc (GCC) 6.1.1 20160609