aboutsummaryrefslogtreecommitdiff
path: root/tcl
diff options
context:
space:
mode:
authorAntonio Borneo <borneo.antonio@gmail.com>2024-03-02 14:01:07 +0100
committerAntonio Borneo <borneo.antonio@gmail.com>2024-03-16 14:42:20 +0000
commit1d076d6ce1908d5c154bfc6ee2ccd8a629853ef1 (patch)
treeb498dc51a2d9f407710db2f09ebab73c6ef0c1d3 /tcl
parente9df8a5102106de5a13956759ae52eb72ff68113 (diff)
downloadriscv-openocd-1d076d6ce1908d5c154bfc6ee2ccd8a629853ef1.zip
riscv-openocd-1d076d6ce1908d5c154bfc6ee2ccd8a629853ef1.tar.gz
riscv-openocd-1d076d6ce1908d5c154bfc6ee2ccd8a629853ef1.tar.bz2
openocd: dump full command line in the debug log
When receiving an OpenOCD debug log to investigate about errors or issues, the first question is often about providing the complete command line to better understand the use context. Plus, when OpenOCD is lunched by an IDE, its command line is kept hidden inside the IDE, adding troubles to the user to recover it. Add the full command line directly inside the debug log. It could have been useful to also search and add in the log the full path of the OpenOCD executable, but this is not an immediate task due to portability among OS's. See, for example: https://stackoverflow.com/questions/933850 This part could be handled in a future change, if really needed. Change-Id: Ia6c5b838b9b7208bf1ecac7f95b5efc319aeabf5 Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com> Reviewed-on: https://review.openocd.org/c/openocd/+/8170 Tested-by: jenkins Reviewed-by: Paul Fertser <fercerpav@gmail.com>
Diffstat (limited to 'tcl')
0 files changed, 0 insertions, 0 deletions