gdb and binutils branch test_pagination_fix created. e882ef3cfc3d991433c3b9aed104961ad3ce5904

gdb and binutils branch test_pagination_fix created. e882ef3cfc3d991433c3b9aed104961ad3ce5904

[simark]

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