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] Make gdb_in_secondary_prompt_p() be per UI
Date: Tue, 21 Jun 2016 12:26:00 -0000 [thread overview]
Message-ID: <dbf30ca3f5fec91671b37592f1a6644a2c36f67a@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT dbf30ca3f5fec91671b37592f1a6644a2c36f67a ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: dbf30ca3f5fec91671b37592f1a6644a2c36f67a
Make gdb_in_secondary_prompt_p() be per UI
gdb/ChangeLog:
2016-06-21 Pedro Alves <palves@redhat.com>
* top.c (gdb_secondary_prompt_depth): Delete.
(gdb_in_secondary_prompt_p): Add ui parameter. Use it.
(gdb_readline_wrapper_cleanup, gdb_readline_wrapper): Adjust to
per-UI gdb_secondary_prompt_depth.
* top.h (struct ui) <secondary_prompt_depth>: New field.
next reply other threads:[~2016-06-21 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 12:26 sergiodj+buildbot [this message]
2016-06-21 12:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master sergiodj+buildbot
2016-06-21 18:57 ` Failures on Debian-i686, " sergiodj+buildbot
2016-06-21 19:26 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-06-21 22:34 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-06-22 17:38 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-06-22 18:01 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-06-22 19:08 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-06-22 20:04 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-06-22 21:26 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-07-15 3:59 ` Failures on Ubuntu-AArch64-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=dbf30ca3f5fec91671b37592f1a6644a2c36f67a@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).