On 2025-11-19 04:31, ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-arm, after: | commit glibc-2.42.9000-514-g8d999a69936 | Author: H. Peter Anvin hpa@zytor.com | Date: Mon Oct 20 13:42:09 2025 -0700 | | linux/termios: clear k_termios.c_cflag & CIBAUD for non-split speed [BZ 33340] | | After getting more experience with the various broken direct-to-ioctl | termios2 hacks using Fedora 43 beta, I have found a fair number of | cases where the software would fail to set, or clear CIBAUD for | ... 29 lines of the commit log omitte
Produces 2 regressions: | | regressions.sum: | Running gdb:gdb.base/term.exp ... | FAIL: gdb.base/term.exp: after last resume: info terminal | FAIL: gdb.base/term.exp: post tcsetattr: info terminal
Used configuration : *CI config* tcwg_gnu_native_check_gdb master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-1753. Please let us know if you have a fix.
I have root caused this test failure to the script assuming that tcgetattr() ... tcsetattr() ... tcgetattr() will always produce a configuration that is bitwise identical to the previous configuration, which is not true with normalization. This is an invalid use of the termios structure, which is mostly an opaque data type, but gdb has a rather unique use case here in that it is a debugger, and as such "it is not bitwise identical but has the same function" might still be a problem for them.
Either way, this I believe is something that needs to be addressed in gdb; either by using the kernel interface directly for the purpose of saving and restoring, alternatively they may need some assistance in the form of a dedicated save/restore interface.
I have filed this bug in the gdb bugzilla to address this issue: