This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/20418] Problems with synchronous commands and new-ui


https://sourceware.org/bugzilla/show_bug.cgi?id=20418

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
Hmm.  Running the console interpreter on the extra UI instead does not trigger
the problem.  I checked now that the MI ui's ui->prompt_state ends up correctly
set to PROMPT_BLOCKED.  It looks like when we emit MI async events
(=library-loaded, etc.), and we go about restoring the previous terminal state,
we end up calling target_terminal_ours, which reinstalls MI's input_fd in the
event loop...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]