"emacs -nw" hangs in a terminal
Wed May 23 16:03:00 GMT 2012
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 finished processing the C-g and goes back
into its idle loop, in which it repeatedly calls select.
gdb doesn't normally show the threads created by select. If it did, it
would always create voluminous output. Can you infer anything from the
fact that it shows this one?
> The problem with stackdumps is that the addresses only make sense
> for a single version of the Cygwin DLL. If that's a self-built
> version, what does `addr2line -e /bin/cygwin1.dll 610CFA77' print?
> If it's 1.7.15, please install the cygwin-debug package and call
> the same addr2line.
> I assume the address corresponds to select.cc, line 625, but I'm
> quite busy with the pthread_cancel stuff, so I didn't look deeper
> into this problem.
Yes, that's correct. (I'm using the 20120516 snapshot.)
>> eax=80106D50 ebx=34322D73 ecx=766231E7 edx=00000000 esi=00000001
>> ebp=048FACC8 esp=048FACA0
>> program=C:\cygwin\home\kbrown\src\emacs\test-nox\src\emacs.exe, pid
>> 6492, thread pipesel
> Yes, that's exactly the created thread. Do you happen to know what
> kind of descriptor has been given to select at this point? Is that
> a pty master side perhaps?
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 through the first call to select after the
longjmp and see exactly where the crash is happening.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin