OK to push Thanks Chris
On 25/3/2023 10:11 am, Karel Gardas wrote: > 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. > --- > tester/rtems/testing/bsps/stm32h7-stlink.ini | 1 + > 1 file changed, 1 insertion(+) > > 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 _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel