This is the mail archive of the 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]

[RFA] Avoid error/prompt reversal for mingw

   I am currently trying to 
run the testsuite of mingw target...
It is almost working now...

One trouble I found when testing this
is that gdb errors
are often misplaced after the return prompt for
the mingw built gdb.

  I don't know if this is really a mingw specific bug
or if it can happen for other targets,
but I found a very easy way to avoid this:
I simply added a gdb_flush (file) 
after the exception test is printed out.

  Is there a reason not to do this?
Or this is patch OK?

Pierre Muller
Pascal language support maintainer for GDB

ChangeLog entry:

2008-03-31  Pierre Muller  <>

	* exceptions.c (print_exception): force flush of file
	after printing of exception message.

$ cvs diff -up gdb/exceptions.c
Index: gdb/exceptions.c
RCS file: /cvs/src/src/gdb/exceptions.c,v
retrieving revision 1.28
diff -u -p -r1.28 exceptions.c
--- gdb/exceptions.c    14 Mar 2008 18:57:43 -0000      1.28
+++ gdb/exceptions.c    31 Mar 2008 15:05:39 -0000
@@ -310,7 +310,7 @@ print_exception (struct ui_file *file, s
   fprintf_filtered (file, "\n");
+  gdb_flush (file);
   /* Now append the annotation.  */
   switch (e.reason)

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