From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Pedro Alves <palves@redhat.com>,
Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>,
Edjunior Machado <emachado@redhat.com>
Subject: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders
Date: Mon, 18 Dec 2017 19:21:00 -0000 [thread overview]
Message-ID: <m3efnrsuyu.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <CAGWvnynqs_19F96cUX_339E0rmppQ4piGnUZzCssYhKULn4Qkg@mail.gmail.com> (David Edelsohn's message of "Fri, 15 Dec 2017 18:20:23 -0500")
On Fri, Dec 15 2017, David Edelsohn wrote:
> Reverting to an earlier revision of the DejaGNU Framework did not help.
>
> I also updated all of the packages installed on the Debian system,
> including the kernel, but the problem still remains. make check is
> reporting a large number of timeouts in gdb.base and gdb.thread. At
> 300s per timeout, it adds up -- eventually to 9 hours. Some of the
> log files are attached.
I can reproduce the hangs with native-gdbserver on s390x; at least for:
display.exp
step-over-trips-on-watchpoint.exp
watchpoint-fork.exp
watchpoints.exp
A bisect shows the culprit:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=c65d6b55
Before this commit I see many FAILs with these tests, but no hangs.
(The FAILs are due to lack of hardware watchpoint support for gdbserver
on s390. At some time I had started a patch for that; maybe I should
revive it...)
Even knowing the first broken commit, I'm not sure yet what causes the
hangs. I'll look more into that tomorrow.
--
Andreas
next prev parent reply other threads:[~2017-12-18 19:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 13:45 Sergio Durigan Junior
2017-12-15 13:54 ` David Edelsohn
2017-12-15 14:20 ` Sergio Durigan Junior
2017-12-15 14:34 ` David Edelsohn
2017-12-15 14:48 ` Pedro Alves
2017-12-15 15:06 ` David Edelsohn
2017-12-15 15:43 ` Pedro Alves
2017-12-15 15:53 ` David Edelsohn
2017-12-15 16:20 ` Pedro Alves
2017-12-15 17:29 ` David Edelsohn
2017-12-15 18:55 ` David Edelsohn
2017-12-15 19:20 ` Pedro Alves
2017-12-15 23:20 ` David Edelsohn
2017-12-18 19:21 ` Andreas Arnez [this message]
2017-12-15 14:49 ` Sergio Durigan Junior
2017-12-15 21:19 ` Yao Qi
2017-12-15 22:40 ` David Edelsohn
2017-12-15 23:19 ` Sergio Durigan Junior
2017-12-19 10:12 ` Joel Brobecker
2017-12-19 11:15 ` Yao Qi
2018-01-15 22:29 ` [BuildBot] Notifications re-enabled for the Debian-s390x-* builders (was: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders) Sergio Durigan Junior
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=m3efnrsuyu.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=emachado@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
/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: link
Be 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).