On Sat, 2019-03-09 at 16:39 +0100, Corinna Vinschen wrote:
> On Mar 8 23:44, Peter Kozich (UM) wrote:
> > On Fri, 2019-03-08 at 23:21 +0100, Peter Kozich (UM) wrote:
> > > [...]
> > > I tested this:
> > >
> > > https://cygwin.com/snapshots/x
On Mar 9 18:48, Ken Brown wrote:
> On 3/9/2019 10:38 AM, Corinna Vinschen wrote:
> > On Mar 9 12:35, Ken Brown wrote:
> >> On 3/8/2019 5:03 PM, Ken Brown wrote:
> >>> On 3/8/2019 3:22 PM, Corinna Vinschen wrote:
> Ken, any chance you could test this as well? If there really are still
>
On 3/9/2019 10:38 AM, Corinna Vinschen wrote:
> On Mar 9 12:35, Ken Brown wrote:
>> On 3/8/2019 5:03 PM, Ken Brown wrote:
>>> On 3/8/2019 3:22 PM, Corinna Vinschen wrote:
Ken, any chance you could test this as well? If there really are still
hangs with current emacs and the 0308 snapsho
On Mar 8 23:44, Peter Kozich (UM) wrote:
> On Fri, 2019-03-08 at 23:21 +0100, Peter Kozich (UM) wrote:
> > [...]
> > I tested this:
> >
> > https://cygwin.com/snapshots/x86/cygwin1-20190306.dll.xz
> >
> > emacs was on for a long time, did n
On Mar 8 21:27, Rockefeller, Harry wrote:
> [snip]
> > > > > peter@D11934N ~
> > > > > $ 1 [main] emacs 489 C:\CygWin\bin\emacs-w32.exe: *** fatal
> > > > > error -
> > > > > CreateThread failed for pipesel - 0x0<0x0>, Win32 error 8
> > > >
> > > > I couldn't directly reproduce this issue, b
On Mar 9 12:35, Ken Brown wrote:
> On 3/8/2019 5:03 PM, Ken Brown wrote:
> > On 3/8/2019 3:22 PM, Corinna Vinschen wrote:
> >> Ken, any chance you could test this as well? If there really are still
> >> hangs with current emacs and the 0308 snapshot, I might need a bit of
> >> help. Some kind of
On 3/8/2019 5:03 PM, Ken Brown wrote:
> On 3/8/2019 3:22 PM, Corinna Vinschen wrote:
>> On Mar 8 20:10, Rockefeller, Harry wrote:
>> peter@D11934N ~
>> $ 1 [main] emacs 489 C:\CygWin\bin\emacs-w32.exe: *** fatal
>> error -
>> CreateThread failed for pipesel - 0x0<0x0>, Win32
ter Kozich (UM) wrote:
> > > In response to this one:
> > >
> > > Re: Fork issue with timerfd
> > >
> > >From: Achim Gratz
> > >To: cygwin at cygwin dot com
> > > Dat
I made a mistake, the correct snapshot I tested is this:
https://cygwin.com/snapshots/x86/cygwin1-20190306.dll.xz
On Wed, 2019-03-06 at 22:23 +0100, Corinna Vinschen wrote:
> On Mar 6 21:54, Peter Kozich (UM) wrote:
> > In response to this one:
> >
> > Re: Fo
On 3/8/2019 3:22 PM, Corinna Vinschen wrote:
> On Mar 8 20:10, Rockefeller, Harry wrote:
> peter@D11934N ~
> $ 1 [main] emacs 489 C:\CygWin\bin\emacs-w32.exe: *** fatal
> error -
> CreateThread failed for pipesel - 0x0<0x0>, Win32 error 8
I couldn't directly reprodu
[snip]
> > > > peter@D11934N ~
> > > > $ 1 [main] emacs 489 C:\CygWin\bin\emacs-w32.exe: *** fatal
> > > > error -
> > > > CreateThread failed for pipesel - 0x0<0x0>, Win32 error 8
> > >
> > > I couldn't directly reproduce this issue, but I saw emacs using
> > > more an more memory while the
On Mar 8 20:10, Rockefeller, Harry wrote:
> > > > peter@D11934N ~
> > > > $ 1 [main] emacs 489 C:\CygWin\bin\emacs-w32.exe: *** fatal
> > > > error -
> > > > CreateThread failed for pipesel - 0x0<0x0>, Win32 error 8
> > >
> > > I couldn't directly reproduce this issue, but I saw emacs using
> > >
> > > Re: Fork issue with timerfd
> > >
> > >From: Achim Gratz
> > >To: cygwin at cygwin dot com
>
> > >Subject: Re: Fork issue with timerfd
> > >
> > >
> > >
>
On Wed, 2019-03-06 at 22:23 +0100, Corinna Vinschen wrote:
> On Mar 6 21:54, Peter Kozich (UM) wrote:
> > In response to this one:
> >
> > Re: Fork issue with timerfd
> >
> >From: Achim Gratz
> >To: cygwin at cygwin dot com
> >
On Mar 6 21:54, Peter Kozich (UM) wrote:
> In response to this one:
>
> Re: Fork issue with timerfd
>
>From: Achim Gratz
>To: cygwin at cygwin dot com
>Date: Tue, 05 Mar 2019 20:15:32 +0100
> Subject: Re:
In response to this one:
Re: Fork issue with timerfd
From: Achim Gratz
To: cygwin at cygwin dot com
Date: Tue, 05 Mar 2019 20:15:32 +0100
Subject: Re: Fork issue with timerfd
Anyway, the latest snapshot seemingly resolved that issue as
Ken Brown writes:
> On 3/4/2019 1:13 PM, Achim Gratz wrote:
>> I consistently see that problem with the latest snapshot 20190303 when
>> trying to save a changed document from emacs-w32. I didn't try
>> emacs-X11 and emacs-nox doesn't exhibit the problem (or rarely enough
>> that I got through the
On 3/4/2019 1:13 PM, Achim Gratz wrote:
> Ken Brown writes:
>> I've been using emacs extensively on both x86 and x86_64 with the latest
>> snapshot, and I've had no further problems. I think 3.0.2 is ready to go.
>
> I consistently see that problem with the latest snapshot 20190303 when
> trying
Ken Brown writes:
> I've been using emacs extensively on both x86 and x86_64 with the latest
> snapshot, and I've had no further problems. I think 3.0.2 is ready to go.
I consistently see that problem with the latest snapshot 20190303 when
trying to save a changed document from emacs-w32. I did
On Feb 27 16:31, Ken Brown wrote:
> On 2/27/2019 11:19 AM, Corinna Vinschen wrote:
> > On Feb 26 13:39, Ken Brown wrote:
> >> On 2/26/2019 4:48 AM, Corinna Vinschen wrote:
> >>> On Feb 26 09:57, Corinna Vinschen wrote:
> On Feb 26 00:01, Ken Brown wrote:
> > I did get the following, howeve
On 2/27/2019 11:19 AM, Corinna Vinschen wrote:
> On Feb 26 13:39, Ken Brown wrote:
>> On 2/26/2019 4:48 AM, Corinna Vinschen wrote:
>>> On Feb 26 09:57, Corinna Vinschen wrote:
On Feb 26 00:01, Ken Brown wrote:
> I did get the following, however, during one of the trials (while emacs
On Feb 26 13:39, Ken Brown wrote:
> On 2/26/2019 4:48 AM, Corinna Vinschen wrote:
> > On Feb 26 09:57, Corinna Vinschen wrote:
> >> On Feb 26 00:01, Ken Brown wrote:
> >>> I did get the following, however, during one of the trials (while emacs
> >>> was idle):
> >>>
> >>> 1 [main] emacs 246 C:\Use
On 2/26/2019 4:48 AM, Corinna Vinschen wrote:
> On Feb 26 09:57, Corinna Vinschen wrote:
>> On Feb 26 00:01, Ken Brown wrote:
>>> On 2/25/2019 3:20 PM, Corinna Vinschen wrote:
On Feb 25 11:03, Corinna Vinschen wrote:
> On Feb 25 03:21, Ken Brown wrote:
>> On 2/24/2019 9:23 PM, Ken Brow
On Feb 26 09:57, Corinna Vinschen wrote:
> On Feb 26 00:01, Ken Brown wrote:
> > On 2/25/2019 3:20 PM, Corinna Vinschen wrote:
> > > On Feb 25 11:03, Corinna Vinschen wrote:
> > >> On Feb 25 03:21, Ken Brown wrote:
> > >>> On 2/24/2019 9:23 PM, Ken Brown wrote:
> > On 2/24/2019 2:52 PM, Corinn
On Feb 26 09:57, Corinna Vinschen wrote:
> On Feb 26 00:01, Ken Brown wrote:
> > On 2/25/2019 3:20 PM, Corinna Vinschen wrote:
> > > On Feb 25 11:03, Corinna Vinschen wrote:
> > >> On Feb 25 03:21, Ken Brown wrote:
> > >>> On 2/24/2019 9:23 PM, Ken Brown wrote:
> > On 2/24/2019 2:52 PM, Corinn
On Feb 26 00:01, Ken Brown wrote:
> On 2/25/2019 3:20 PM, Corinna Vinschen wrote:
> > On Feb 25 11:03, Corinna Vinschen wrote:
> >> On Feb 25 03:21, Ken Brown wrote:
> >>> On 2/24/2019 9:23 PM, Ken Brown wrote:
> On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
> > On Feb 24 20:09, Corinna Vi
On 2/25/2019 3:20 PM, Corinna Vinschen wrote:
> On Feb 25 11:03, Corinna Vinschen wrote:
>> On Feb 25 03:21, Ken Brown wrote:
>>> On 2/24/2019 9:23 PM, Ken Brown wrote:
On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
> On Feb 24 20:09, Corinna Vinschen wrote:
>> On Feb 24 19:55, Corinna
On Feb 25 11:03, Corinna Vinschen wrote:
> On Feb 25 03:21, Ken Brown wrote:
> > On 2/24/2019 9:23 PM, Ken Brown wrote:
> > > On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
> > >> On Feb 24 20:09, Corinna Vinschen wrote:
> > >>> On Feb 24 19:55, Corinna Vinschen wrote:
> > On Feb 24 17:27, Ken
On Feb 25 03:21, Ken Brown wrote:
> On 2/24/2019 9:23 PM, Ken Brown wrote:
> > On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
> >> On Feb 24 20:09, Corinna Vinschen wrote:
> >>> On Feb 24 19:55, Corinna Vinschen wrote:
> On Feb 24 17:27, Ken Brown wrote:
> > I'm seeing sporadic errors like
On 2/24/2019 9:23 PM, Ken Brown wrote:
> On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
>> On Feb 24 20:09, Corinna Vinschen wrote:
>>> On Feb 24 19:55, Corinna Vinschen wrote:
On Feb 24 17:27, Ken Brown wrote:
> I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
> On Feb 24 20:09, Corinna Vinschen wrote:
>> On Feb 24 19:55, Corinna Vinschen wrote:
>>> On Feb 24 17:27, Ken Brown wrote:
I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
emacs:
0 [main] emacs-X11
On Feb 24 20:09, Corinna Vinschen wrote:
> On Feb 24 19:55, Corinna Vinschen wrote:
> > On Feb 24 17:27, Ken Brown wrote:
> > > I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
> > > emacs:
> > >
> > >0 [main] emacs-X11 864 C:\cygwin64\bin\emacs-X11.exe: *** fatal
On Feb 24 19:55, Corinna Vinschen wrote:
> On Feb 24 17:27, Ken Brown wrote:
> > I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
> > emacs:
> >
> >0 [main] emacs-X11 864 C:\cygwin64\bin\emacs-X11.exe: *** fatal
> > error in
> > forked process - Can't recreate sh
On Feb 24 17:27, Ken Brown wrote:
> I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
> emacs:
>
>0 [main] emacs-X11 864 C:\cygwin64\bin\emacs-X11.exe: *** fatal error
> in
> forked process - Can't recreate shared timerfd section during fork!
>0 [main] ema
34 matches
Mail list logo