gdb batch calls time out on armhf

Bug #1926934 reported by Matthias Klose on 2021-05-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdb
Confirmed
Medium
gdb (Ubuntu)
Undecided
Unassigned

Bug Description

seen when trying to build the gcc-10, or gcc-snapshot packages. A lot of tests in the guality test suite time out after 300 seconds (the default dejagnu timeout). These tests, like pr36728-1.c run ok on other architectures (and fail), but timeout on armhf.

Seen in impish with gcc-10 and gcc-snapshot.

Trying to run the gdb 10.2 tests on both hirsute and impish, I see a lot of timeouts as well.

seening this with gdb 10.2 and gcc 10.3.0 on Ubuntu 21.04, using glibc 2.33, binutils 2.26.1 and gcc 10.3.0.

A lot of tests in the guality test suite time out after 300 seconds (the default dejagnu timeout). These tests, like pr36728-1.c run ok on other architectures (and fail), but timeout on armhf.

for gcc,

RUNTESTFLAGS=guality.exp=pr36728-1.c make -e -C <build>/gcc check-gcc

The last "successful" gcc-10 build is from April, using a gdb snapshot taken from the gdb-10 branch on March 05 2021.

Architectures like x86_64, powerpc64le, s390x, aarch64 are not affected.

Changed in gdb:
importance: Unknown → Medium
status: Unknown → Confirmed
Matthias Klose (doko) on 2021-05-05
tags: added: ftbfs

this is "fixed" in the glibc 2.33 branch, if I understand the glibc maintainers correctly, they consider this as a workaround (see PR27744).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.