On 6/3/2012 12:52 PM, Christopher Faylor wrote:
On Sun, Jun 03, 2012 at 08:54:20AM -0400, Ken Brown wrote:
On 6/2/2012 11:08 PM, Christopher Faylor wrote:
On Fri, May 25, 2012 at 04:07:32PM -0400, Ken Brown wrote:
On 5/25/2012 2:49 PM, Ken Brown wrote:
On 5/25/2012 10:35 AM, Corinna Vinschen
On Sun, Jun 03, 2012 at 08:54:20AM -0400, Ken Brown wrote:
>On 6/2/2012 11:08 PM, Christopher Faylor wrote:
>> On Fri, May 25, 2012 at 04:07:32PM -0400, Ken Brown wrote:
>>> On 5/25/2012 2:49 PM, Ken Brown wrote:
On 5/25/2012 10:35 AM, Corinna Vinschen wrote:
> I applied a patch which call
On 6/2/2012 11:08 PM, Christopher Faylor wrote:
On Fri, May 25, 2012 at 04:07:32PM -0400, Ken Brown wrote:
On 5/25/2012 2:49 PM, Ken Brown wrote:
On 5/25/2012 10:35 AM, Corinna Vinschen wrote:
I applied a patch which calls the signal handler after cleanup. The
downside is that the signal handl
On Fri, May 25, 2012 at 04:07:32PM -0400, Ken Brown wrote:
>On 5/25/2012 2:49 PM, Ken Brown wrote:
>> On 5/25/2012 10:35 AM, Corinna Vinschen wrote:
>>> I applied a patch which calls the signal handler after cleanup. The
>>> downside is that the signal handler is only called if select is called
>>>
On 5/25/2012 2:49 PM, Ken Brown wrote:
On 5/25/2012 10:35 AM, Corinna Vinschen wrote:
I applied a patch which calls the signal handler after cleanup. The
downside is that the signal handler is only called if select is called
from the main thread. A better patch would perhaps be to stop all
threa
On 5/25/2012 10:35 AM, Corinna Vinschen wrote:
On May 25 15:03, Corinna Vinschen wrote:
On May 25 08:45, Ken Brown wrote:
On 5/25/2012 6:03 AM, Corinna Vinschen wrote:
And then again, do we know if 24.x works on older Cygwin release or
snapshots? If it's a Cygwin problem, it might help to nai
On May 25 15:03, Corinna Vinschen wrote:
> On May 25 08:45, Ken Brown wrote:
> > On 5/25/2012 6:03 AM, Corinna Vinschen wrote:
> > >And then again, do we know if 24.x works on older Cygwin release or
> > >snapshots? If it's a Cygwin problem, it might help to nail it down.
> >
> > It works on the
On May 25 08:45, Ken Brown wrote:
> On 5/25/2012 6:03 AM, Corinna Vinschen wrote:
> >And then again, do we know if 24.x works on older Cygwin release or
> >snapshots? If it's a Cygwin problem, it might help to nail it down.
>
> It works on the 20120111 snapshot but fails on the 20120122
> snapsho
On 5/25/2012 6:03 AM, Corinna Vinschen wrote:
On May 24 08:17, Ken Brown wrote:
On 5/23/2012 12:02 PM, Corinna Vinschen wrote:
On May 23 11:56, Ken Brown wrote:
Based on the emacs code, I think that's right. But maybe I need to
download the source for the snapshot I'm using (or build cygwin1.
On 2012-05-25 12:03, Corinna Vinschen wrote:
I'll look further into this, but I am wondering about this: Is the new
Fsignal/Fthrow implementation so much different than the old one in
emacs 23.x? If not, why does it work in 23.x? Any chance 24.x produces
a stack or heap corruption? Double free o
On May 24 08:17, Ken Brown wrote:
> On 5/23/2012 12:02 PM, Corinna Vinschen wrote:
> >On May 23 11:56, Ken Brown wrote:
> >>Based on the emacs code, I think that's right. But maybe I need to
> >>download the source for the snapshot I'm using (or build cygwin1.dll
> >>myself) so that I can step thr
On 5/23/2012 12:02 PM, Corinna Vinschen wrote:
On May 23 11:56, Ken Brown wrote:
On 5/23/2012 10:15 AM, Corinna Vinschen wrote:
On May 23 08:00, Ken Brown wrote:
I don't know what this has to do with the longjmp, but the thread
which gets crated right after pressing Ctrl-G is due to a select or
On May 23 11:56, Ken Brown wrote:
> On 5/23/2012 10:15 AM, Corinna Vinschen wrote:
> >On May 23 08:00, Ken Brown wrote:
> >I don't know what this has to do with the longjmp, but the thread
> >which gets crated right after pressing Ctrl-G is due to a select or
> >poll call. The descriptor is a pipe
On 5/23/2012 10:15 AM, Corinna Vinschen wrote:
On May 23 08:00, Ken Brown wrote:
I don't know what this has to do with the longjmp, but the thread
which gets crated right after pressing Ctrl-G is due to a select or
poll call. The descriptor is a pipe, fifo, or pty.
After the longjmp, emacs has
On May 23 08:00, Ken Brown wrote:
> I've gotten some more information from gdb. The crash occurs after
> a call to _longjmp, and gdb shows a new thread created right at that
> point. This doesn't happen when I run emacs under X instead of in
> mintty. Here's an excerpt from the gdb session, with
On 5/22/2012 9:49 AM, Corinna Vinschen wrote:
On May 22 15:41, Corinna Vinschen wrote:
On May 22 07:42, Ken Brown wrote:
On 5/22/2012 7:28 AM, Corinna Vinschen wrote:
On May 21 14:51, Ken Brown wrote:
On 5/21/2012 12:29 PM, Corinna Vinschen wrote:
On May 21 11:31, Ken Brown wrote:
On 5/21/2
On May 22 15:41, Corinna Vinschen wrote:
> On May 22 07:42, Ken Brown wrote:
> > On 5/22/2012 7:28 AM, Corinna Vinschen wrote:
> > >On May 21 14:51, Ken Brown wrote:
> > >>On 5/21/2012 12:29 PM, Corinna Vinschen wrote:
> > >>>On May 21 11:31, Ken Brown wrote:
> > On 5/21/2012 6:02 AM, Ken Brown
On May 22 07:42, Ken Brown wrote:
> On 5/22/2012 7:28 AM, Corinna Vinschen wrote:
> >On May 21 14:51, Ken Brown wrote:
> >>On 5/21/2012 12:29 PM, Corinna Vinschen wrote:
> >>>On May 21 11:31, Ken Brown wrote:
> On 5/21/2012 6:02 AM, Ken Brown wrote:
> I've discovered something strange by ru
On 5/22/2012 7:28 AM, Corinna Vinschen wrote:
On May 21 14:51, Ken Brown wrote:
On 5/21/2012 12:29 PM, Corinna Vinschen wrote:
On May 21 11:31, Ken Brown wrote:
On 5/21/2012 6:02 AM, Ken Brown wrote:
On 5/21/2012 4:50 AM, Filipp Gunbin wrote:
emacs-24.0.96-2 crashes when I am doing the follo
On May 21 14:51, Ken Brown wrote:
> On 5/21/2012 12:29 PM, Corinna Vinschen wrote:
> >On May 21 11:31, Ken Brown wrote:
> >>On 5/21/2012 6:02 AM, Ken Brown wrote:
> >>>On 5/21/2012 4:50 AM, Filipp Gunbin wrote:
> emacs-24.0.96-2 crashes when I am doing the following:
>
> 1) emacs -Q -n
On 5/21/2012 12:29 PM, Corinna Vinschen wrote:
On May 21 11:31, Ken Brown wrote:
On 5/21/2012 6:02 AM, Ken Brown wrote:
On 5/21/2012 4:50 AM, Filipp Gunbin wrote:
emacs-24.0.96-2 crashes when I am doing the following:
1) emacs -Q -nw
2) M-x shell
3) C-x C-f C-g
I can reproduce this. I'll tr
On May 21 11:31, Ken Brown wrote:
> On 5/21/2012 6:02 AM, Ken Brown wrote:
> >On 5/21/2012 4:50 AM, Filipp Gunbin wrote:
> >>emacs-24.0.96-2 crashes when I am doing the following:
> >>
> >>1) emacs -Q -nw
> >>2) M-x shell
> >>3) C-x C-f C-g
> >
> >I can reproduce this. I'll try again to fix it.
>
On 5/21/2012 6:02 AM, Ken Brown wrote:
On 5/21/2012 4:50 AM, Filipp Gunbin wrote:
emacs-24.0.96-2 crashes when I am doing the following:
1) emacs -Q -nw
2) M-x shell
3) C-x C-f C-g
I can reproduce this. I'll try again to fix it.
I've discovered something strange by running emacs under gdb.
On 5/21/2012 4:50 AM, Filipp Gunbin wrote:
emacs-24.0.96-2 crashes when I am doing the following:
1) emacs -Q -nw
2) M-x shell
3) C-x C-f C-g
I can reproduce this. I'll try again to fix it.
Thanks for the report.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ:
> From: Filipp Gunbin
>
> I started emacs-23.4.2 as usual (emacs -nw) and it did not hang.
>
> emacs-24.0.96-2 also seems to work normally, I've used it for some time
> without problems and will continue with it.
>
emacs-24.0.96-2 crashes when I am doing the following:
1) emacs -Q -nw
2) M-x
> From: Ken Brown
>
> I think I've fixed this, in both emacs-23 and emacs-24. Please retest
> once I announce that the new releases have been uploaded (23.4-2 and
> 24.0.96-2).
>
I started emacs-23.4.2 as usual (emacs -nw) and it did not hang.
emacs-24.0.96-2 also seems to work normally, I'
On 5/15/2012 10:27 AM, Filipp Gunbin wrote:
[Ken Brown wrote:]
I can reproduce this on XP but not on Windows 7. And I see from your
(partial) cygcheck output that you're running Vista. I'll try to debug
this on my XP system.
I think I've fixed this, in both emacs-23 and emacs-24. Please rete
>
> I wonder if this is the same problem as the one that was reported in
>
>http://cygwin.com/ml/cygwin/2012-05/msg00292.html
>
> and fixed in the 2012-05-14 snapshot.
I tried that snapshot, but it didn't help. Both cygcheck and emacs-24 still
dump core.
>
> I can reproduce this on XP b
On 5/15/2012 8:26 AM, Filipp Gunbin wrote:
Sorry, the message disappeared for some reason. Here it is.
Filipp
Ken Brown writes:
On 5/15/2012 6:57 AM, Filipp Gunbin wrote:
I tried emacs-24, but with no luck: after hitting `C-x C-f C-g' emacs
almost always dumps core. I had to revert to emac
Sorry, the message disappeared for some reason. Here it is.
Filipp
Ken Brown writes:
> On 5/15/2012 6:57 AM, Filipp Gunbin wrote:
>> I tried emacs-24, but with no luck: after hitting `C-x C-f C-g' emacs
>> almost always dumps core. I had to revert to emacs-23 for now (using
>> the workaround w
cygcheck.out.1
Description: Binary data
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
On 5/15/2012 6:57 AM, Filipp Gunbin wrote:
I tried emacs-24, but with no luck: after hitting `C-x C-f C-g' emacs
almost always dumps core. I had to revert to emacs-23 for now (using
the workaround with emacs-nox, thanks for it!).
Sorry for the poor report, probably I could provide more details
Ken Brown writes:
> On 5/14/2012 8:29 AM, Ken Jackson wrote:
>> Recently, emacs in a terminal started hanging:
>>
>>/usr/bin/emacs -nw --no-init-file --no-site-file
>>
>> I had to kill it from another terminal window.
>>
>> But I noticed /usr/bin/emacs points through alternatives to
>> /usr/b
On 5/14/2012 8:29 AM, Ken Jackson wrote:
Recently, emacs in a terminal started hanging:
/usr/bin/emacs -nw --no-init-file --no-site-file
I had to kill it from another terminal window.
But I noticed /usr/bin/emacs points through alternatives to
/usr/bin/emacs-X11, so I started calling /usr/
Recently, emacs in a terminal started hanging:
/usr/bin/emacs -nw --no-init-file --no-site-file
I had to kill it from another terminal window.
But I noticed /usr/bin/emacs points through alternatives to
/usr/bin/emacs-X11, so I started calling /usr/bin/emacs-nox
directly. (Actually I modifie
35 matches
Mail list logo
