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] mi_load_progress: Restore current_uiout using a scoped_restore
Date: Sat, 16 Sep 2017 12:47:00 -0000 [thread overview]
Message-ID: <5846367a24e24f334077ceb7f7389acbd072b11a@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 5846367a24e24f334077ceb7f7389acbd072b11a ***
Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 5846367a24e24f334077ceb7f7389acbd072b11a
mi_load_progress: Restore current_uiout using a scoped_restore
Simply use a scoped_restore instead of manually saving and restoring
current_uiout.
gdb/ChangeLog:
* mi/mi-main.c (mi_load_progress): Restore current_uiout using a
scoped_restore.
next reply other threads:[~2017-09-16 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 12:47 sergiodj+buildbot [this message]
2017-09-16 12:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-09-16 12:57 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-09-16 13:41 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-09-16 13:45 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-09-16 13:49 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-09-16 14:11 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-09-16 14:12 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-16 14:18 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-08 4:00 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2017-10-08 22:16 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-10-12 13:22 ` Failures on Debian-s390x-native-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=5846367a24e24f334077ceb7f7389acbd072b11a@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).