git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Improve QNX support in GIT

From
Mike Gorchak <mike.gorchak.qnx@gmail.com>
Date
Feb 26, 2013, 18:54 UTC
Message-ID
<CAHXAxrOnRkqFEtYa2DN4FEwzeXpKhLsUx0yvoi59dtOSyEGOQw@mail.gmail.com>
In-Reply-To
<20130226172504.GA2271@ftbfs.org>
Show 6 quoted lines
> I don't think it's a good idea to just enable thread support.  On QNX,
> once a process creates a thread, fork stops working.  This breaks
> commands that create threads and then try to run other programs, such
> as "git fetch" with an https remote.  If threads are enabled, I think
> that the uses of fork need to be audited and, if they can be called
> after a thread is created, fixed.

I did a quick look into the run-command.c and transport-helper.c modules, they use pthread OR fork for external command spawning depending on NO_PTHREAD declaration. Another fork() occurence in the module daemon.c for daemonization and I know that it works.

Previous: Mike Gorchak
Message 4 of 4 in “Re: [PATCH] Improve QNX support in GIT”
  1. Matt KraaiFeb 26, 2013
  2. David MichaelFeb 26, 2013
  3. Mike GorchakFeb 26, 2013
  4. Mike GorchakFeb 26, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.