From: Pedro Alves <palves@redhat.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: 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: Fri, 15 Dec 2017 19:20:00 -0000 [thread overview]
Message-ID: <6cf34fdb-c33e-33c1-7dcd-816438f04a0d@redhat.com> (raw)
In-Reply-To: <CAGWvny=RyKfXdMXuzZphGfS7_mYN0+gsausbK-VRx0--V4F+DQ@mail.gmail.com>
On 12/15/2017 06:55 PM, David Edelsohn wrote:
> Older DejaGNU does not seem to have an effect. All of the processes
> are stuck in "gdb.threads/process-dies-while-handling-bp"
>
Strange, I'm not seeing any potential infinite loop in the
testcase, so I'd expect that it least it should timeout properly.
Can you run the testcase alone, with
make check TESTS="gdb.threads/process-dies-while-handling-bp"
and send the resulting gdb.sum/gdb.log.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-12-15 19:20 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 [this message]
2017-12-15 23:20 ` David Edelsohn
2017-12-18 19:21 ` Andreas Arnez
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=6cf34fdb-c33e-33c1-7dcd-816438f04a0d@redhat.com \
--to=palves@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=emachado@redhat.com \
--cc=gdb-patches@sourceware.org \
--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).