Hello,

El lun, 19 ene 2026, 9:17, zhangdandan <[email protected]> escribió:

> Source: gdb
> Version: 17.1-1
> Severity: normal
> Tags: ftbfs, forky, sid
> User: [email protected]
> Usertags: loong64
>
> Dear maintainers,
>
> Compiling the gdb 17.1-1 failed for loong64 in the Debian Package
> Auto-Building environment.
> The error log is as follows,
> ```
>          === gdb tests ===
>
> Schedule of variations:
>      native-gdbserver
>
> Running target native-gdbserver
> Using
> /build/reproducible-path/gdb-17.1/gdb/testsuite/boards/../boards/native-gdbserver.exp
>
> as board description file for target.
> Using
> /build/reproducible-path/gdb-17.1/gdb/testsuite/boards/../boards/gdbserver-base.exp
>
> as board description file for target.
> Using
> /build/reproducible-path/gdb-17.1/gdb/testsuite/boards/../boards/local-board.exp
>
> as board description file for target.
> Using
> /build/reproducible-path/gdb-17.1/gdb/testsuite/config/gdbserver.exp as
> tool-and-target-specific interface file.
> Running
> /build/reproducible-path/gdb-17.1/gdb/testsuite/gdb.base/breakpoint-in-ro-region.exp
>
> ...
> FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: auto-hw
> on: step in ro region
> FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted off: auto-hw
> on: thread advanced
> FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted on: auto-hw
> on: step in ro region
> FAIL: gdb.base/breakpoint-in-ro-region.exp: always-inserted on: auto-hw
> on: thread advanced
>
>          === gdb Summary ===
>
> # of expected passes        36
> # of unexpected failures    4
> ......
> ```
> The full build log of gdb can be found at
>
> https://buildd.debian.org/status/fetch.php?pkg=gdb&arch=loong64&ver=17.1-1&stamp=1768551317&raw=0
> .
>
> After local analysis and reproduction, there are currently no new findings.
> The gdb is blocking the building of over 100 software packages.
> Please help analyze and troubleshoot the issue.
>

Could you reproduce these issues with upstream GDB 17.1 or latest snapshot?

Regards

>

Reply via email to