[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10044: "warning: reader_thread.SetEvent failed with 6 for fd -1" and
From: |
Eli Zaretskii |
Subject: |
bug#10044: "warning: reader_thread.SetEvent failed with 6 for fd -1" and accessing fd_info[-1] |
Date: |
Mon, 14 Nov 2011 19:14:21 +0200 |
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 14 Nov 2011 16:33:42 +0100
>
> which means that cp->fd is being used as an index into fd_info[], and
> the choice between _sys_wait_accept and _sys_read_ahead is bogus.
>
> IIUC, cp->fd == -1 means that the wait was intended, but no input is
> expected, so I think the following patch is enough:
>
>
> === modified file 'src/w32proc.c'
> --- src/w32proc.c 2011-06-24 21:25:22 +0000
> +++ src/w32proc.c 2011-11-14 15:19:09 +0000
> @@ -241,7 +241,8 @@
>
> /* We have to wait for the go-ahead before we can start */
> if (cp == NULL
> - || WaitForSingleObject (cp->char_consumed, INFINITE) != WAIT_OBJECT_0)
> + || WaitForSingleObject (cp->char_consumed, INFINITE) != WAIT_OBJECT_0
> + || cp->fd < 0)
> return 1;
>
> for (;;)
Let's go for it, thanks.
Does this patch by chance solve a similar bogus DebPrint message each
time a versioned file under bzr control is visited?