On 6/11/2019 12:42 PM, Michael Haubenwallner wrote:
>
>
> On 6/11/19 10:48 AM, Corinna Vinschen wrote:
>> Hi Ken,
>>
>> On Jun 8 12:20, Ken Brown wrote:
>>> On 6/7/2019 5:43 PM, Ken Brown wrote:
On 6/7/2019 3:13 PM, Ken Brown wrote:
> On 6/7/2019 2:31 PM, Achim Gratz wrote:
>> Ken B
On 6/11/19 10:48 AM, Corinna Vinschen wrote:
> Hi Ken,
>
> On Jun 8 12:20, Ken Brown wrote:
>> On 6/7/2019 5:43 PM, Ken Brown wrote:
>>> On 6/7/2019 3:13 PM, Ken Brown wrote:
On 6/7/2019 2:31 PM, Achim Gratz wrote:
> Ken Brown writes:
>> I think I've found the problem. I was mish
Hi Ken,
On Jun 8 12:20, Ken Brown wrote:
> On 6/7/2019 5:43 PM, Ken Brown wrote:
> > On 6/7/2019 3:13 PM, Ken Brown wrote:
> >> On 6/7/2019 2:31 PM, Achim Gratz wrote:
> >>> Ken Brown writes:
> I think I've found the problem. I was mishandling signals that arrived
> during a
> re
On 6/7/2019 5:43 PM, Ken Brown wrote:
> On 6/7/2019 3:13 PM, Ken Brown wrote:
>> On 6/7/2019 2:31 PM, Achim Gratz wrote:
>>> Ken Brown writes:
I think I've found the problem. I was mishandling signals that arrived
during a
read. But after I fix that, there's still one nagging issu
On 6/7/2019 3:13 PM, Ken Brown wrote:
> On 6/7/2019 2:31 PM, Achim Gratz wrote:
>> Ken Brown writes:
>>> I think I've found the problem. I was mishandling signals that arrived
>>> during a
>>> read. But after I fix that, there's still one nagging issue involving
>>> timerfd
>>> code. I'll writ
Achim Gratz writes:
> Anything triggering a race or deadlock will depend on so many other
> things that it really is no surprise to see seemingly unrelated changes
> making the bug appear or disappear. There are certainly races left in
> Cygwin, I see them from time to time in various Perl modules
On 6/7/2019 2:31 PM, Achim Gratz wrote:
> Ken Brown writes:
>> I think I've found the problem. I was mishandling signals that arrived
>> during a
>> read. But after I fix that, there's still one nagging issue involving
>> timerfd
>> code. I'll write to the main list with details. I *think* it
Ken Brown writes:
> I think I've found the problem. I was mishandling signals that arrived
> during a
> read. But after I fix that, there's still one nagging issue involving
> timerfd
> code. I'll write to the main list with details. I *think* it's a timerfd
> bug,
> but it's puzzling tha
On 6/3/2019 12:35 PM, Corinna Vinschen wrote:
> On May 30 12:56, Ken Brown wrote:
>> On 5/26/2019 11:10 AM, Ken Brown wrote:
>>> fhandler_pipe is currently the only class derived from
>>> fhandler_base_overlapped. This patch series rewrites parts of
>>> fhandler_pipe so that it can be derived from
On May 30 12:56, Ken Brown wrote:
> On 5/26/2019 11:10 AM, Ken Brown wrote:
> > fhandler_pipe is currently the only class derived from
> > fhandler_base_overlapped. This patch series rewrites parts of
> > fhandler_pipe so that it can be derived from fhandler_base instead.
> > We can then simplify
On 5/26/2019 11:10 AM, Ken Brown wrote:
> fhandler_pipe is currently the only class derived from
> fhandler_base_overlapped. This patch series rewrites parts of
> fhandler_pipe so that it can be derived from fhandler_base instead.
> We can then simplify the code by removing fhandler_base_overlappe
fhandler_pipe is currently the only class derived from
fhandler_base_overlapped. This patch series rewrites parts of
fhandler_pipe so that it can be derived from fhandler_base instead.
We can then simplify the code by removing fhandler_base_overlapped.
In particular, this gets rid of the peculiar
12 matches
Mail list logo
