Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: force output at predictable points in ending-run.c
Date: Fri, 11 Jan 2002 22:51:00 -0000	[thread overview]
Message-ID: <20020112065251.549665E9D8@zwingli.cygnus.com> (raw)


2002-01-12  Jim Blandy  <jimb@redhat.com>

	* gdb.base/ending-run.c (main): Avoid messing with setvbuf; just
	call `fflush' after every `printf', so that the output is produced
	at predictable points, regardless of whatever buffering does (or
	doesn't) take place.
	* gdb.base/ending-run.exp: Adjust tests to expect output to appear
	at different points.

Index: gdb/testsuite/gdb.base/ending-run.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/ending-run.c,v
retrieving revision 1.4
diff -c -r1.4 ending-run.c
*** gdb/testsuite/gdb.base/ending-run.c	2001/09/18 17:50:36	1.4
--- gdb/testsuite/gdb.base/ending-run.c	2002/01/12 06:47:54
***************
*** 22,33 ****
      int i;
  
      p = (int *) malloc( 4 );
!     setvbuf (stdout, alloca (64), _IOLBF, 64);
      for (i = 1; i < 10; i++)
          {
              printf( "%d ", callee( i ));
!             
          }
!     printf( " Goodbye!\n" );
      return 0;
  }
--- 22,33 ----
      int i;
  
      p = (int *) malloc( 4 );
! 
      for (i = 1; i < 10; i++)
          {
              printf( "%d ", callee( i ));
!             fflush (stdout);
          }
!     printf( " Goodbye!\n" ); fflush (stdout);
      return 0;
  }
Index: gdb/testsuite/gdb.base/ending-run.exp
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/ending-run.exp,v
retrieving revision 1.23
diff -c -r1.23 ending-run.exp
*** gdb/testsuite/gdb.base/ending-run.exp	2001/11/10 22:27:26	1.23
--- gdb/testsuite/gdb.base/ending-run.exp	2002/01/12 06:47:54
***************
*** 129,138 ****
  # See if we can step out with control.  The "1 2 3" stuff
  # is output from the program.
  #
! gdb_test "cont" ".*Breakpoint.*31.*"
  
  if ![gdb_skip_stdio_test "Step to return"] {
!     gdb_test "next" ".*1 2 7 14 23 34 47 62 79  Goodbye!.*32.*" \
  	    "Step to return"
  } else {
      gdb_test "next" "" ""
--- 129,138 ----
  # See if we can step out with control.  The "1 2 3" stuff
  # is output from the program.
  #
! gdb_test "cont" ".*1 2 7 14 23 34 47 62 79.*Breakpoint.*31.*"
  
  if ![gdb_skip_stdio_test "Step to return"] {
!     gdb_test "next" ".*Goodbye!.*32.*" \
  	    "Step to return"
  } else {
      gdb_test "next" "" ""


             reply	other threads:[~2002-01-12  6:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 22:51 Jim Blandy [this message]
2002-01-20 16:25 ` Andrew Cagney
2002-01-21  8:31 ` Fernando Nasser
2002-01-21 14:12   ` Jim Blandy

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=20020112065251.549665E9D8@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    /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