Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA] Avoid error/prompt reversal for mingw
Date: Mon, 31 Mar 2008 15:29:00 -0000	[thread overview]
Message-ID: <000601c89342$3eb4a590$bc1df0b0$@u-strasbg.fr> (raw)

   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  <muller@ics.u-strasbg.fr>

	* 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)
     {







             reply	other threads:[~2008-03-31 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 15:29 Pierre Muller [this message]
2008-03-31 15:57 ` Daniel Jacobowitz
2008-03-31 16:04   ` Pierre Muller
2008-03-31 17:34     ` 'Daniel Jacobowitz'

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000601c89342$3eb4a590$bc1df0b0$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox