public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] testsuite: Add replay logging to GDBSERVER_DEBUG
Date: Fri, 17 May 2019 16:26:00 -0000	[thread overview]
Message-ID: <b420b89e4b321ff31f2e76cac499b908f042069b@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT b420b89e4b321ff31f2e76cac499b908f042069b ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: b420b89e4b321ff31f2e76cac499b908f042069b

testsuite: Add replay logging to GDBSERVER_DEBUG

Add "replay" to the list of GDBSERVER_DEBUG options.  This will
cause a gdbserver.replay file to be written to the test output
directory.

At the same time switch this to a comma separated list in order
to easily handle all possible options.

The replay log is created by GDB, but has been added to
GDBSERVER_DEBUG as it is only required for gdbserver tests. To
enable it, the gdb_debug_init is overridden to allow the additional
checking, before calling the original function.

gdb/testsuite/ChangeLog:

        * README (Testsuite Parameters): Add replay logging to
        GDBSERVER_DEBUG.
        (gdbserver,debug): Refer to GDBSERVER_DEBUG.
        * lib/gdbserver-support.exp (gdbserver_start): Treat gdbserverdebug
        as a comma separated list.
        (gdb_debug_init): Override procedure.


             reply	other threads:[~2019-05-17 16:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 16:26 sergiodj+buildbot [this message]
2019-05-17 16:27 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2019-05-17 22:50 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2019-05-17 23:08 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2019-05-17 23:12 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-05-17 23:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2019-05-17 23:25 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2019-05-17 23:27 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2019-05-17 23:37 ` Failures on Fedora-i686, " sergiodj+buildbot
2019-05-17 23:55 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2019-05-19 19:54 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2019-05-20  3:04 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2019-05-20 15:30 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot

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=b420b89e4b321ff31f2e76cac499b908f042069b@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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: 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).