From: Bernd Petrovitsch <bernd@firmix.at>
To: Sino <szj087@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: the different effect of system call fork()
Date: Wed, 08 Apr 2009 15:08:48 +0200 [thread overview]
Message-ID: <1239196128.5031.3.camel@spike.firmix.at> (raw)
In-Reply-To: <cab3445d0904080553k6fc67498s73cb5b7c661ff0b@mail.gmail.com>
Hi!
On Wed, 2009-04-08 at 20:53 +0800, Sino wrote:
[...]
> I don't know whether this is the right place for this email, but I
It's probably not.
> post it here since it concerns the system call of fork.
> here is my fwo source code.
>
> //fork1.cc
[...]
> if (pid_t pid = fork() < 0)
I don't think that this line does what you want it to do.
Hint: Using a "pid_t" for the boolean result for a comparison seems
strange at best.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2009-04-08 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 12:53 Sino
2009-04-08 13:08 ` Bernd Petrovitsch [this message]
2009-04-09 12:36 ` Nick Andrew
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=1239196128.5031.3.camel@spike.firmix.at \
--to=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=szj087@gmail.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
all inboxes | Powered by JetHome®