From: Matt Kraai <kraai@ftbfs.org>
To: Mike Gorchak <mike.gorchak.qnx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Improve QNX support in GIT
Date: Tue, 26 Feb 2013 12:13:05 -0800 [thread overview]
Message-ID: <20130226201305.GA3502@ftbfs.org> (raw)
Hi,
Please include me in the Cc field, since I'm not subscribed to the
list.
Mike Gorchak wrote:
> Do you have a testcase for this (without using git codebase)? I wrote
> numerous resource managers since QNX 6.0 using threads and fork()s for
> daemonization in different order and never experienced a problems.
> There can be issues with pipes in case of external command run.
I just created the following one:
#include <pthread.h>
#include <stdio.h>
#include <string.h>
#include <errno.h>
#include <sys/types.h>
#include <process.h>
static void *
start_routine (void *arg)
{
return NULL;
}
int
main (int argc, char **argv)
{
int err;
if ((err = pthread_create (NULL, NULL, start_routine, NULL)))
{
fprintf (stderr, "foo: pthread_create failed: %s\n", strerror (errno));
return 1;
}
if (fork () == -1)
{
fprintf (stderr, "foo: fork failed: %s\n", strerror (errno));
return 1;
}
return 0;
}
When I compile and run it on either QNX 6.3.2 or QNX 6.5.0, it
produces the following output:
foo: fork failed: Function not implemented
If I remove the call to pthread_create, it doesn't output anything and
exits successfully.
next reply other threads:[~2013-02-26 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 20:13 Matt Kraai [this message]
2013-02-26 20:32 ` [PATCH] Improve QNX support in GIT Mike Gorchak
2013-02-26 20:53 ` Johannes Sixt
2013-02-26 21:02 ` Matt Kraai
-- strict thread matches above, loose matches on Subject: below --
2013-02-26 17:25 Matt Kraai
2013-02-26 18:09 ` David Michael
2013-02-26 18:36 ` Mike Gorchak
2013-02-26 18:54 ` Mike Gorchak
2013-02-23 22:02 Mike Gorchak
2013-02-24 7:36 ` Mike Gorchak
2013-02-24 8:46 ` Junio C Hamano
2013-02-24 14:12 ` Mike Gorchak
2013-02-24 21:24 ` Junio C Hamano
2013-02-25 7:14 ` Junio C Hamano
2013-02-25 8:30 ` Mike Gorchak
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=20130226201305.GA3502@ftbfs.org \
--to=kraai@ftbfs.org \
--cc=git@vger.kernel.org \
--cc=mike.gorchak.qnx@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;
as well as URLs for NNTP newsgroup(s).