"emacs -nw" hangs in a terminal
Tue May 22 13:42:00 GMT 2012
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 running emacs under gdb. If I
> >>>>start emacs-24 in a terminal (but not under X) and start a shell as
> >>>>you did, then every press of C-g creates a new thread, and these are
> >>>>never destroyed. I'm pretty sure the threads are created by Cygwin,
> >>>>not by emacs.
> >Somehow I'm not able to test this. When I start `emacs -Q -nw' in cmd
> >or mintty, emacs takes 100% CPU for some reason. It doesn't matter if I
> >try it under Cygwin 1.7.15 or current CVS.
> That's strange. All my tests were done in mintty. Would it help if
> I sent some strace output and/or a gdb backtrace? I assumed you
> could get those (or at least the strace output) yourself, and I
> didn't want to spam the list.
> P.S. BTW, I tested today's snapshot, and the problem is still there.
I doubt that an strace is sufficient, but you could send me one created
with the latest snapshot off-list, to the address I'm using in the
Changelogs. Please point out the places which seem suspicious to you.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin