On 4/26/25 22:38, ci_not...@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 gdb-16-branchpoint-1244-g5ea1eec52f4
| Author: Tom de Vries <tdevr...@suse.de>
| Date: Wed Apr 9 08:59:42 2025 +0200
|
| [gdb/tdep] Handle ldaex and stlex in
{thumb,arm}_deal_with_atomic_sequence_raw
|
| The Linaro CI reported a regression [1] in test-case
| gdb.base/step-over-syscall.exp due to commit 674d4856730
("[gdb/testsuite] Fix
| gdb.base/step-over-syscall.exp with glibc 2.41").
| ... 100 lines of the commit log omitted.
Produces 4 regressions 4 fixes:
|
| regressions.sum:
| Running gdb:gdb.base/step-over-syscall.exp ...
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off:
check_pc_after_cross_syscall: single step over fork final pc
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: pc after stepi
matches insn addr after syscall
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on:
check_pc_after_cross_syscall: single step over fork final pc
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: pc after stepi
matches insn addr after syscall
|
| fixes.sum:
| Running gdb:gdb.base/step-over-syscall.exp ...
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: continue to
syscall insn fork (the program exited)
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: find syscall
insn in fork
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: single step
over fork (the program is no longer running)
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: break on
syscall insn
Hi,
I've looked at this, and AFAICT this is PR32817 (
https://sourceware.org/bugzilla/show_bug.cgi?id=32817 ).
This is unrelated to the mentioned commit.
Thanks,
- Tom
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-1570.
Please let us know if you have a fix.
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
*
https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/artifact/artifacts/00-sumfiles/
The full lists of regressions and improvements as well as configure and make
commands are in
*
https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
*
https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/artifact/artifacts/sumfiles/xfails.xfail
Current build :
https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/artifact/artifacts
Reference build :
https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1991/artifact/artifacts
Instruction to reproduce the build :
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/5ea1eec52f47fbc9155bd8f057d26429e6881628/tcwg_gnu_native_check_gdb/master-arm/reproduction_instructions.txt
Full commit :
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5ea1eec52f47fbc9155bd8f057d26429e6881628
_______________________________________________
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
