public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Kurt Roeckx <Q@ping.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wait() and strace -f
Date: Wed, 19 Dec 2001 00:32:33 +0900	[thread overview]
Message-ID: <87itb4v90u.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20011218021407.A1595@ping.be>
In-Reply-To: <20011218021407.A1595@ping.be>

Kurt Roeckx <Q@ping.be> writes:

> int     main()
> {
>         int     i;
> 
>         if (!fork())
>         {
>                 /* Child 1. */
>                 return 0;
>         }
> 
>         if (!fork())
>         {
>                 /* Child 2. */
>                 sleep(10);
>                 return 0;
>         }
> 
>         /* Parent. */
>         sleep(1);
>         wait(&i);
>         return 0;
> }
> 
> Without strace -f, this program stops after 1 second and the
> second child still lives for 9 seconds.  With strace -f this
> program stops after 10 second after the second child died.
> 
> I think it's related to strace being the "real" parent of the
> child.  But that doesn't really explain why I need 2 childs.

Probably, it's feature (or bug) of strace. If the trace process has
child, trace of a child is continued before wait() of parent. Then,
exit() of the child process continue wait() of parent.

>         if (!fork())
>         {
>                 /* Child 1. */
		  sleep(2);
>                 return 0;
>         }

The above continued the parent after 2 seconds.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2001-12-18 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18  1:14 wait() and strace -f Kurt Roeckx
2001-12-18 15:32 ` OGAWA Hirofumi [this message]
     [not found] ` <877krlc60x.fsf@devron.myhome.or.jp>
2001-12-18 20:18   ` Kurt Roeckx
2001-12-19 15:26     ` OGAWA Hirofumi

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=87itb4v90u.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=Q@ping.be \
    --cc=linux-kernel@vger.kernel.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