Bug 17171 - reprint prompt after asynchronous output
Summary: reprint prompt after asynchronous output
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: cli (show other bugs)
Version: HEAD
: P2 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-17 10:11 UTC by dje
Modified: 2014-07-17 14:54 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
Project(s) to access:
ssh public key:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dje 2014-07-17 10:11:28 UTC 
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.
Comment 1 Pedro Alves 2014-07-17 14:54:21 UTC 
Yeah.

I had a prototype patch for that somewhere ...

*looks*

... here:

https://www.sourceware.org/ml/gdb-patches/2012-11/msg00786.html