This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Flush ^running
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Sat, 4 Oct 2008 19:01:40 +0400
- Subject: Flush ^running
I've run into a case where gdb would not print ^running in response
to -exec-continue -- at least not during the time frontend is willing
to wait for the response. The problem only happened for my when gdb
is driven by a frontend, not on command line; I don't know what frontend
does differently. I've checked in the below patch to fix this.
- Volodya
Index: gdb/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.9872
diff -u -p -r1.9872 ChangeLog
--- gdb/ChangeLog 3 Oct 2008 22:00:09 -0000 1.9872
+++ gdb/ChangeLog 4 Oct 2008 14:56:26 -0000
@@ -1,3 +1,7 @@
+2008-10-04 Vladimir Prus <vladimir@codesourcery.com>
+
+ * mi/mi-interp.c (mi_on_resume): Flush raw_stdout.
+
2008-10-03 Paul Pluzhnikov <ppluzhnikov@google.com>
PR gdb/2384:
Index: gdb/mi/mi-interp.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-interp.c,v
retrieving revision 1.35
diff -u -p -r1.35 mi-interp.c
--- gdb/mi/mi-interp.c 5 Jul 2008 17:57:24 -0000 1.35
+++ gdb/mi/mi-interp.c 4 Oct 2008 14:56:26 -0000
@@ -362,6 +362,7 @@ mi_on_resume (ptid_t ptid)
if (!target_is_async_p ())
fputs_unfiltered ("(gdb) \n", raw_stdout);
}
+ gdb_flush (raw_stdout);
}
extern initialize_file_ftype _initialize_mi_interp; /* -Wmissing-prototypes */