aboutsummaryrefslogtreecommitdiff
path: root/git-hooks/commit-msg
diff options
context:
space:
mode:
authorParshintsev Anatoly <anatoly.parshintsev@syntacore.com>2024-03-21 07:07:23 +0300
committerParshintsev Anatoly <anatoly.parshintsev@syntacore.com>2024-04-24 02:34:48 +0300
commit665fbf605b04e4ea2ad9af1c789f1b11588ec863 (patch)
tree60bec3ad0235858f45957d906e96ab86032a08c8 /git-hooks/commit-msg
parent3991492cc101f4289be06ec7dc23c6ad7748a74a (diff)
downloadriscv-openocd-665fbf605b04e4ea2ad9af1c789f1b11588ec863.zip
riscv-openocd-665fbf605b04e4ea2ad9af1c789f1b11588ec863.tar.gz
riscv-openocd-665fbf605b04e4ea2ad9af1c789f1b11588ec863.tar.bz2
fix confusing status messages during resume
Recently, (after b503fdef02f) OpenOCD started to notify user about hart state updates. This causes confusion in some cases since some internal updates to the hart state should not be visible to the user as these are implementation details. For example situation like this: ``` > reset halt JTAG tap: riscv.tap tap/device found: 0xdeadbeef ... > resume [riscv.cpu0] Found 4 triggers riscv.cpu0 halted due to single-step. [riscv.cpu1] Found 4 triggers riscv.cpu1 halted due to single-step. [riscv.cpu2] Found 4 triggers riscv.cpu2 halted due to single-step. [riscv.cpu3] Found 4 triggers riscv.cpu3 halted due to single-step. ``` likely confuse people. There is no issue with the resume functionality. It`s just that resume internally causes single-step that causes hart state to change. This commit disable calling of user-specified (and default) callbacks during the "hidden" step operation disabling these confusing messages Change-Id: I3412a089e2abdcd315d86cec7ee732fdd18c1601 Signed-off-by: Parshintsev Anatoly <anatoly.parshintsev@syntacore.com>
Diffstat (limited to 'git-hooks/commit-msg')
0 files changed, 0 insertions, 0 deletions