Bug 27810 - gdb times out on a lot of test cases in both the gdb and gcc test suites (arm-linux-gnueabihf)
Summary: gdb times out on a lot of test cases in both the gdb and gcc test suites (arm...
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-03 06:23 UTC by Matthias Klose
Modified: 2021-05-05 10:40 UTC (History)
1 user (show)

See Also:
Host:
Target: arm-linux-gnueabihf
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Klose 2021-05-03 06:23:31 UTC 
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.
Comment 1 Matthias Klose 2021-05-05 10:40:21 UTC 
this is "fixed" in the glibc 2.33 branch, if I understand the glibc maintainers correctly, they consider this as a workaround (see PR27744).