public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: simark@sourceware.org To: src-cvs@sourceware.org Subject: gdb and binutils branch test_pagination_fix created. e882ef3cfc3d991433c3b9aed104961ad3ce5904 Date: Mon, 15 Dec 2014 16:51:00 -0000 [thread overview] Message-ID: <20141215165132.14775.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, test_pagination_fix has been created at e882ef3cfc3d991433c3b9aed104961ad3ce5904 (commit) - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e882ef3cfc3d991433c3b9aed104961ad3ce5904 commit e882ef3cfc3d991433c3b9aed104961ad3ce5904 Author: Simon Marchi <simon.marchi@ericsson.com> Date: Mon Dec 15 11:46:44 2014 -0500 testsuite: expect possible pagination when starting gdb When gdb starts, the lines that appear before the first prompt may get paginated if the terminal in which the tests are ran is too small (in terms of rows). These lines include the welcome/license message and possibly more, such as "Reading symbols from...". Pagination is disabled right after gdb is started (with "set height 0"), but this output happens before we are able to set height. If these lines get paginated, gdb waits for the user to press enter and the test harness waits for gdb to print its prompt, resulting in a deadlock. My first idea was to launch gdb with --quiet. However, some lines are still printed ("Reading symbols from...", some more stuff when attaching with --pid, etc). The proposed solution simply expects that pagination can occur after starting gdb. If this is the case, it sends a "\n" and loops. gdb/testsuite/Changelog: * lib/gdb.exp (default_gdb_start): After starting gdb, loop as long as we get pagination notifications. ----------------------------------------------------------------------- hooks/post-receive -- gdb and binutils
reply other threads:[~2014-12-15 16:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141215165132.14775.qmail@sourceware.org \ --to=simark@sourceware.org \ --cc=src-cvs@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: linkBe 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).