Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Edjunior Machado <edjunior@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,
	Sergio Durigan Junior <sergiodj@redhat.com>,
		Pedro Alves <palves@redhat.com>,
	GDB Patches <gdb-patches@sourceware.org>,
		David Edelsohn <dje.gcc@gmail.com>,
	Edjunior Machado <emachado@redhat.com>
Subject: Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume
Date: Mon, 15 Jan 2018 17:37:00 -0000	[thread overview]
Message-ID: <CAJJrRvYOE64R_NEqhhjoS9BP7Bnwc6Bxy18rGUcp-hJ8aGEefg@mail.gmail.com> (raw)
In-Reply-To: <CAH=s-POSOGChGGzM-iwTceSS8vw8cZbibdWnT2smk-kM32K=Cw@mail.gmail.com>

Hi all,

On Mon, Jan 15, 2018 at 3:52 PM, Yao Qi <qiyaoltc@gmail.com> wrote:

> On Mon, Jan 15, 2018 at 2:43 PM, Andreas Arnez <arnez@linux.vnet.ibm.com>
> wrote:
> >
> > Sergio, now that this is in, we should be able to re-activate the
> > reporting for the s390 (and Power) Buildbots, right?
> >
>
> I am not sure ppc64 issue is resolved.  See
> https://sourceware.org/ml/gdb-patches/2017-12/msg00414.html
> Note that I had a patch to fix fails in
> gdb.threads/process-dies-while-handling-bp.exp
> in this thread, but the tests with gdbserver still hang in some watchpoint
> tests.
>
>
Andreas' patch does fix the gdb.base/watchpoint.exp hang on ppc64*
native-gdbserver, but as Yao mentioned, it is still hanging on
gdb.threads/process-dies-while-handling-bp.exp without his fix (
https://sourceware.org/ml/gdb-patches/2017-12/msg00434.html).

That said, just tested upstream testsuite, with Andreas' patch included,
plus Yao's aforementioned patch and native-gdbserver testrun no longer
hangs. These are the results I got with native-gdbserver on Fedora26:

ppc64le:
                === gdb Summary ===

# of expected passes            50410
# of unexpected failures        550
# of unexpected successes       3
# of expected failures          58
# of unknown successes          4
# of known failures             64
# of unresolved testcases       5
# of untested testcases         49
# of unsupported tests          171
/home/fedora/binutils-gdb.git/build/gdb/gdb version  8.1.50.20180115-git
-nw -nx -data-directory
/home/fedora/binutils-gdb.git/build/gdb/testsuite/../data-directory  -ex
"set auto-connect-native-target off"

ppc64:
                === gdb Summary ===

# of expected passes            50133
# of unexpected failures        1109
# of unexpected successes       3
# of expected failures          58
# of unknown successes          4
# of known failures             65
# of unresolved testcases       6
# of untested testcases         51
# of unsupported tests          162
/home/fedora/binutils-gdb.git/build/gdb/gdb version  8.1.50.20180115-git
-nw -nx -data-directory
/home/fedora/binutils-gdb.git/build/gdb/testsuite/../data-directory  -ex
"set auto-connect-native-target off"

(FWIW, at first glance, gdb.linespec/cpcompletion.exp in ppc64 BE seems to
be one of the main culprits for the whole testrun taking longer (~1h) and
with considerably more failures than in ppc64le, aparently due to the
ppc64's function descriptor.)

Please let me know if you need any additional testing.

Thanks and regards,
Edjunior


  parent reply	other threads:[~2018-01-15 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 16:56 Andreas Arnez
2018-01-12 19:11 ` [pushed + testcase] " Pedro Alves
2018-01-15 14:43   ` Andreas Arnez
2018-01-15 14:53     ` Yao Qi
2018-01-15 15:22       ` Andreas Arnez
2018-01-15 16:10         ` Yao Qi
2018-01-15 17:37       ` Edjunior Machado [this message]
2018-01-15 18:17         ` Pedro Alves
2018-01-15 20:11           ` Sergio Durigan Junior
2018-01-15 15:18     ` 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=CAJJrRvYOE64R_NEqhhjoS9BP7Bnwc6Bxy18rGUcp-hJ8aGEefg@mail.gmail.com \
    --to=edjunior@gmail.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=emachado@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.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