public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27810] New: gdb times out on a lot of test cases in both the gdb and gcc test suites (arm-linux-gnueabihf) Date: Mon, 03 May 2021 06:23:31 +0000 [thread overview] Message-ID: <bug-27810-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27810 Bug ID: 27810 Summary: gdb times out on a lot of test cases in both the gdb and gcc test suites (arm-linux-gnueabihf) Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: doko at debian dot org Target Milestone: --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-05-03 6:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 6:23 doko at debian dot org [this message] 2021-05-03 6:23 ` [Bug gdb/27810] " doko at debian dot org 2021-05-05 10:40 ` doko at debian dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27810-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).