DASH Shell discussions
 help / color / mirror / Atom feed
From: Anders Kaseorg <andersk@MIT.EDU>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: dash@vger.kernel.org, git@packages.debian.org
Subject: Re: [PATCH] Set SA_RESTART flag on SIGCHLD handler
Date: Fri, 22 Jun 2012 05:36:12 -0400	[thread overview]
Message-ID: <4FE43C8C.2040809@mit.edu> (raw)
In-Reply-To: <20120622003628.GD4730@burratino>

On 06/21/2012 08:36 PM, Jonathan Nieder wrote:
> Thanks.  Here's a less invasive patch to experiment with.

Hmm.  I’ve kicked off several builds in the git-core PPA, first under 
dash with the original patch, now under dash with the less invasive 
patch.  Under either dash, almost all of the builds end up trapped in 
what looks like a deadlock, at various parts of t9010-svn-fe.sh.

https://launchpad.net/~git-core/+archive/ppa/+build/3596228
https://launchpad.net/~git-core/+archive/ppa/+build/3596229
https://launchpad.net/~git-core/+archive/ppa/+build/3597370
https://launchpad.net/~git-core/+archive/ppa/+build/3597371

I’ll try to debug this later by hacking up the package to run that 
script through strace -fiv during build (since I still can’t reproduce 
locally), unless you have anything more clever to try.

Anders


  parent reply	other threads:[~2012-06-22  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F665E77.3060102@mit.edu>
     [not found] ` <20120319025201.GA24778@burratino>
     [not found]   ` <4F66A6CA.4010002@mit.edu>
     [not found]     ` <20120319033751.GA25237@burratino>
2012-06-21  7:48       ` [PATCH] Set SA_RESTART flag on SIGCHLD handler Anders Kaseorg
     [not found]         ` <20120622003628.GD4730@burratino>
2012-06-22  9:36           ` Anders Kaseorg [this message]
2012-06-26 10:03             ` Anders Kaseorg
2012-06-26 12:19               ` Anders Kaseorg
2012-07-21 23:14                 ` Anders Kaseorg
2012-06-22 22:02           ` Jilles Tjoelker

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=4FE43C8C.2040809@mit.edu \
    --to=andersk@mit.edu \
    --cc=dash@vger.kernel.org \
    --cc=git@packages.debian.org \
    --cc=jrnieder@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