[PATCH][PR gdb/21690] Fix interruption of command history search

[PATCH][PR gdb/21690] Fix interruption of command history search

[Hannes Domani]

If you press Ctrl-C during an incremental search of the readline history, the
prompt is reset, but readline is still in the incremental search mode.

The call of rl_callback_sigcleanup cleans up the internal readline state, and
disables the incremental search mode.

gdb/ChangeLog:

2020-04-25  Hannes Domani  <ssbssa@yahoo.de>

	PR gdb/21690
	* main.c (start_event_loop): Call rl_callback_sigcleanup.
---
 gdb/main.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gdb/main.c b/gdb/main.c
index 59cb14161b..a8c1d3ccb1 100644
--- a/gdb/main.c
+++ b/gdb/main.c
@@ -55,6 +55,8 @@
 #include "gdbsupport/alt-stack.h"
 #include "observable.h"
 
+#include "readline/readline.h"
+
 /* The selected interpreter.  This will be used as a set command
    variable, so it should always be malloc'ed - since
    do_setshow_command will free it.  */
@@ -371,6 +373,8 @@ start_event_loop ()
 	     in a messed-up state.  Reset it here.  */
 	  current_ui->prompt_state = PROMPT_NEEDED;
 	  gdb::observers::command_error.notify ();
+	  /* Clean up internal state of the callback interface.  */
+	  rl_callback_sigcleanup ();
 	  /* This call looks bizarre, but it is required.  If the user
 	     entered a command that caused an error,
 	     after_char_processing_hook won't be called from
-- 
2.26.2