> > You have to start your watcher before looping, otherwise it does return when
> > no other watchers are active.
>
> *sigh*
>
> But since I may not _want_ to start watch signals in the child until much
> later, I don't have a watcher I want to start, unless I make one up
When you have no watch
On Wed, Jan 16, 2008 at 03:48:52AM +0100, Marc Lehmann wrote:
> On Tue, Jan 15, 2008 at 12:54:59PM -0500, Chris Shoemaker <[EMAIL PROTECTED]>
> wrote:
> > I've narrowed this down considerably by tracing both good and bad
> > executions and comparing. I'll comment the differences in the code:
>
>
On Tue, Jan 15, 2008 at 12:54:59PM -0500, Chris Shoemaker <[EMAIL PROTECTED]>
wrote:
> I've narrowed this down considerably by tracing both good and bad
> executions and comparing. I'll comment the differences in the code:
Your test program is still buggy:
> ev_default_fork();
> ev_loop
On Tue, Jan 15, 2008 at 10:50:34AM -0500, Chris Shoemaker wrote:
> On Tue, Jan 15, 2008 at 05:06:27AM +0100, Marc Lehmann wrote:
> > On Mon, Jan 14, 2008 at 10:56:54AM -0500, Chris Shoemaker <[EMAIL
> > PROTECTED]> wrote:
> > > I believe the attached program demonstrates some bug related to si
On Tue, Jan 15, 2008 at 05:06:27AM +0100, Marc Lehmann wrote:
> On Mon, Jan 14, 2008 at 10:56:54AM -0500, Chris Shoemaker <[EMAIL PROTECTED]>
> wrote:
> > I believe the attached program demonstrates some bug related to signal
> > delivery after a fork.
>
> Oh, what you see is that ev_default_
On Mon, Jan 14, 2008 at 10:56:54AM -0500, Chris Shoemaker <[EMAIL PROTECTED]>
wrote:
> I believe the attached program demonstrates some bug related to signal
> delivery after a fork.
Oh, what you see is that ev_default_fork only sets a flag for the next run
of ev_loop. You will have to run ev
On Mon, Jan 14, 2008 at 10:56:54AM -0500, Chris Shoemaker <[EMAIL PROTECTED]>
wrote:
> Hi,
> I believe the attached program demonstrates some bug related to signal
> delivery after a fork.
Thanks for the test program, I will have a look asap.
--
The choice of a Deliant
Hi,
I believe the attached program demonstrates some bug related to signal
delivery after a fork.
I expect the child to receive the HUP signal, run the signal_cb, and exit.
Notice the locking that ensures that the ev_signal is started before
any signal is sent.
This program behaves as I expec
