On Tue, 20 Jan 2026 22:36:47 -0500 Sergio Durigan Junior
<[email protected]> wrote:
On Monday, 19 January 2026, Tiezhu Yang wrote:
...
> I tested on Fedora42, Loongnix25 and Debian for LoongArch64, the test
> passed, so I think there may be some differences for the build system
> environment, please check or install the latest Debian system if
> possible.
Thanks for testing and providing more details.
Am I correct to assume that the problem is not reproducible with the
latest unstable?
Yes, I can not reproduce the problem with the upstream mainline [1],
upstream 17.1 [2], debian 17.1-1 [3] and debian 17.1-2 [4] code with
the same test steps [5] on the debian system [6].
(1) upstream mainline
git clone https://sourceware.org/git/binutils-gdb.git gdb
cd gdb
git checkout master
cd ..
(2) upstream 17.1
git clone https://sourceware.org/git/binutils-gdb.git gdb
cd gdb
git checkout gdb-17.1-release
cd ..
(3) debian 17.1-1
git clone https://salsa.debian.org/gdb-team/gdb.git gdb
cd gdb
git checkout debian/17.1-1
cd ..
(4) debian 17.1-2
git clone https://salsa.debian.org/gdb-team/gdb.git gdb
cd gdb
git checkout debian/17.1-2
cd ..
(5) test steps
rm -rf build && mkdir -p build && cd build
../gdb/configure
make -j"$(nproc)"
make check-gdb TESTS="gdb.base/breakpoint-in-ro-region.exp"
make check-gdb RUNTESTFLAGS="--target_board=native-gdbserver"
TESTS="gdb.base/breakpoint-in-ro-region.exp"
(6) debian system
https://cdimage.debian.org/cdimage/ports/snapshots/2025-12-06/debian-13.0.0-loong64-NETINST-1.iso
Thanks,
Tiezhu
