summaryrefslogtreecommitdiffstats
path: root/tester
diff options
context:
space:
mode:
authorKarel Gardas <karel@functional.vision>2023-03-25 00:10:55 +0100
committerKarel Gardas <karel@functional.vision>2023-03-27 07:05:56 +0200
commiteaf14a654b528b44de14f9da9919555e54324e0d (patch)
treeea00e20c0d574fc5d6494ed31a1930c781a01c19 /tester
parentrtems-bsps-riscv.ini: Update list to drop medany and add BSPs (diff)
downloadrtems-tools-eaf14a654b528b44de14f9da9919555e54324e0d.tar.bz2
tester/bsps: change stm32h7-stlink to handle SIGTRAP as a nostop
The ST-Link GDB server throws spurious SIGTRAP into the GDB sometimes. When this happen, the gdb exits immediately as it's run in batch/script manner. Unfortunately this may be while testcase itself is still running and does not have enough time to print all the required output. Such testcase is then marked as failed although otherwise it may run well to its end. Adding handle of SIGTRAP as a nostop means that GDB will not exit after receiving SIGTRAP but rather be forced to continue as nothing would happen and the running testcase will have a chance to finish its business.
Diffstat (limited to 'tester')
-rw-r--r--tester/rtems/testing/bsps/stm32h7-stlink.ini1
1 files changed, 1 insertions, 0 deletions
diff --git a/tester/rtems/testing/bsps/stm32h7-stlink.ini b/tester/rtems/testing/bsps/stm32h7-stlink.ini
index bf57bee..2c375f5 100644
--- a/tester/rtems/testing/bsps/stm32h7-stlink.ini
+++ b/tester/rtems/testing/bsps/stm32h7-stlink.ini
@@ -40,4 +40,5 @@ gdb_script = bsp_gdb_script
requires = bsp_tty_dev, bsp_gdb_script, target_pretest_command, target_posttest_command
bsp_gdb_script = target extended-remote :61234
load
+ handle SIGTRAP nostop
cont