Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] testsuite: Fix a racy FAIL on gdb.base/multi-forks.exp
Date: Fri, 13 Mar 2009 23:11:00 -0000	[thread overview]
Message-ID: <20090313230033.GB30693@adacore.com> (raw)
In-Reply-To: <20090313194932.GA5597@host0.dyn.jankratochvil.net>

> gdb/testsuite/
> 2009-03-13  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	Fix a racy FAIL.
> 	* gdb.base/multi-forks.exp (continue_to_exit_bp_loc): New function with
> 	code from `follow parent, print pids'.
> 	(`follow child, print pids', `follow parent, print pids'): Call it.
> 	Replace `gdb_test "break..."' by gdb_breakpoint.

This seems pretty reasonable to me...

> +# Continue till where $exit_bp_loc points at eating all the inferior output
> +# which could otherwise corrupt our later communication with GDB.

I am so sorry to be picking on your comments. I very much appreciate
the fact that you spend the time writing them, especially since most
people tend to not write comments. In this case, this comments also
sounds strange. Here is a suggestion:

# Insert a breakpoint at the location provided by the exit_bp_loc global
# and resume the execution until hitting that breakpoint.  We also make
# sure to consume all the expected output from all processes as well,
# to make sure it doesn't cause trouble during a subsequent test.

-- 
Joel


  reply	other threads:[~2009-03-13 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 16:01 Jan Kratochvil
2009-03-13 16:47 ` Joel Brobecker
2009-03-13 21:02   ` Jan Kratochvil
2009-03-13 23:11     ` Joel Brobecker [this message]
2009-03-14 21:45       ` Jan Kratochvil
2009-03-14 12:32   ` Eli Zaretskii

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=20090313230033.GB30693@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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