Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1279574

Bug#1125934: gdb: there are 4 unexpected failures on loong64

Show all headers | View raw

On 2026/1/24 下午2:11, Miao Wang wrote:
> Control: tags -1 - unreproducible
> 
> Hi,
> 
>> 2026年1月24日 13:23，Tiezhu Yang <yangtiezhu@loongson.cn> 写道：
>>
>> On 2026/1/23 下午10:30, Miao Wang wrote:
>>> 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.
>>
>> Could you please check whether CONFIG_HAVE_HW_BREAKPOINT is set in your
>> kernel config? It is usually set by default via the defconfig.
> 
> Apparently yes. The kernel I have used is from Debian. As I've
> explained in my pervious reply, the reason why hardware watch points is
> not supported in my environment is that qemu does not support this. However,
> I guess that gdb fails to set hardware breakpoints might probably be the
> failure reason for the buildds, but the root cause can't be the same, since
> the kernel used by the buildds is shown in the logs and is also from
> Debian ports, 6.17.12+deb14-loong64.
> 
>> IMO the problem is related with the Linux kernel config
>> CONFIG_HAVE_HW_BREAKPOINT which is set by default in the
>> newer kernel used by Debian official ISO:
>>
>> https://cdimage.debian.org/cdimage/ports/snapshots/2025-12-06/debian-13.0.0-loong64-NETINST-1.iso
>>
>> So in order to avoid the problem, one way is to redeploy the above ISO
>> for the builder, the other way is to modify the GDB test case.
> 
> Apparently this conclusion is not correct since in the kernel used
> by buildds, the above config is enabled, unless the kernel is not
> what was in the ports repo with the same name. If it were the kernel
> problem, there would be no need to reinstall the whole system but
> replacing the kernel would be enough. I suspect that this issue
> might be related to the sbuild unshare environment or related to
> how the buildd are deployed. The root cause for it should be further
> investigated.
> 
>> Please send a patch for GDB or let me know that you don't plan to do it
>> and I'll do it.

I do not know the details of the builder environment.

Anyway, as I described in the previous reply [1], tested with the
official Debian ISO [2] on a physical machine, it should support
the hardware breakpoints, the testcases should pass. If tested on
a virtual machine, it needs to adjust the testcases to make them
happy.

Let us wait for the loongarch64 builders to be redeployed and
see if that solves the issue [3].

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125934#20
[2] 
https://cdimage.debian.org/cdimage/ports/snapshots/2025-12-06/debian-13.0.0-loong64-NETINST-1.iso
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125934#46

Thanks,
Tiezhu

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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
      Bug#1125934: gdb: there are 4 unexpected failures on loong64 Sergio Durigan Junior <sergiodj@debian.org> - 2026-01-30 22:30 +0100
        Bug#1125934: gdb: there are 4 unexpected failures on loong64 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2026-02-04 10:00 +0100
          Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-02-04 11:10 +0100
            Bug#1125934: gdb: there are 4 unexpected failures on loong64 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2026-02-04 13:30 +0100
              Bug#1125934: gdb: there are 4 unexpected failures on loong64 Sergio Durigan Junior <sergiodj@debian.org> - 2026-02-06 15:40 +0100
                Bug#1125934: gdb: there are 4 unexpected failures on loong64 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> - 2026-02-06 16:20 +0100
                Bug#1125934: gdb: there are 4 unexpected failures on loong64 Tiezhu Yang <yangtiezhu@loongson.cn> - 2026-02-13 11:30 +0100

csiph-web