Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1279492
| From | Miao Wang <shankerwangmiao@gmail.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1125934: gdb: there are 4 unexpected failures on loong64 |
| Date | 2026-01-23 15:40 +0100 |
| Message-ID | <Mgqul-cHHF-1@gated-at.bofh.it> (permalink) |
| References | <MeSEp-bF4H-5@gated-at.bofh.it> <MfAFr-c8bb-1@gated-at.bofh.it> <MfMng-cfMo-9@gated-at.bofh.it> <MeSEp-bF4H-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Wed, 21 Jan 2026 14:47:19 -0500 Sergio Durigan Junior <sergiodj@debian.org> wrote: > OK, then let's wait for the loongarch64 builders to be redeployed and > see if that solves the issue. > Hi, I managed to reproduce the error in qemu emulated virtual machine, which lacks the support of hardware watch point. The failed test case breakpoint-in-ro-region.exp attempts to set the memory region of the debugged program read-only and force the use of hard breakpoint. The test bench itself takes the case where breakpoint is not supported into account, but failed to notice the slight difference of the output when using gdbserver. That's why the test runs well with normal gdb but fails with gdb server. The attached patch can fix the above issue. However, I have no idea why on the buildd environment, hardware breakpoints cannot be set by gdb. Cheers, Miao Wang
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1125934: gdb: there are 4 unexpected failures on loong64 zhangdandan <zhangdandan@loongson.cn> - 2026-01-19 09:20 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Hector Oron <zumbi@debian.org> - 2026-01-19 09:40 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 zhangdandan <zhangdandan@loongson.cn> - 2026-01-19 09:50 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-01-19 10:40 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Sergio Durigan Junior <sergiodj@debian.org> - 2026-01-21 04:40 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-01-21 08:50 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-01-21 08:20 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Sergio Durigan Junior <sergiodj@debian.org> - 2026-01-21 20:50 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Miao Wang <shankerwangmiao@gmail.com> - 2026-01-23 15:40 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-01-24 06:30 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-01-24 08:00 +0100
Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-01-26 19:00 +0100
csiph-web