Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In gdb_check master-aarch64, after: | gdb patch https://patchwork.sourceware.org/patch/133110 | Author: Markus Metzger | Date: Wed Apr 15 07:23:08 2026 +0000 | | [PATCH v8 1/4] gdb, infrun, btrace: fix reverse/replay stepping at end of execution history | | When trying to step over a breakpoint at the end of the trace, the | step-over will fail with no-history. This does not clear step_over_info | so a subsequent resume will cause GDB to not resume the thread and expect | ... 19 lines of the commit log omitted. | ... applied on top of baseline commit: | c51032987a8 ld: Move "-O 0" option to binutils 2.47 section Used configuration : *CI config* tcwg_gdb_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10098/archive/artifacts/artifacts.precommit/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10098/archive/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10098/archive/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10098/archive/artifacts/ Reference build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-build/builds/10089/archive/artifacts/ Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.