Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug#593426: zsh: Status of background jobs not updated
- X-seq: zsh-workers 28175
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Bug#593426: zsh: Status of background jobs not updated
- Date: Thu, 19 Aug 2010 21:22:51 -0700
- Cc: 593426@xxxxxxxxxxxxxxx
- In-reply-to: <20100818210959.2a9d4d25@pws-pc>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20100818025148.13456.14691.reportbug@xxxxxxxxxxxxxxxxxxxxx> <20100818182959.GA29785@xxxxxxxx> <20100818210959.2a9d4d25@pws-pc>
On Aug 18, 9:09pm, Peter Stephenson wrote:
}
} + } else if (sig == SIGCONT) {
} + Job jn;
} + Process pn;
} + if (findproc(pid, &jn, &pn, 0)) {
} + if (WIFSTOPPED(pn->status))
} + pn->status = SP_RUNNING;
} + }
} + }
Hmm, are we really guaranteed that the job has started running again
just because we killed it with SIGCONT? E.g., if the reason it was
stopped is because it got a TTIN or TTOU, is there a possible race
here because it's just going to immediately stop again?
--
Messages sorted by:
Reverse Date,
Date,
Thread,
Author