From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20079 invoked by alias); 17 Jul 2014 10:11:29 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 20051 invoked by uid 48); 17 Jul 2014 10:11:29 -0000 From: "dje at google dot com" To: gdb-prs@sourceware.org Subject: [Bug cli/17171] New: reprint prompt after asynchronous output Date: Thu, 17 Jul 2014 10:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: dje at google dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q3/txt/msg00111.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17171 Bug ID: 17171 Summary: reprint prompt after asynchronous output Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: dje at google dot com IWBN if gdb reprinted the prompt after asynchronous output (e.g. thread state changes). Even better would be to first delete the old prompt, print the asynchronous output, and then reprint the prompt (plus any text entered by the user up to that point). As things are today, the prompt can get lost in the middle of a lot of asynchronous output, and even if the user can find it s/he can be left confused as to whether gdb is waiting for input. -- You are receiving this mail because: You are on the CC list for the bug.