This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: emacs-X11 freezes with mouse cut and paste
- From: "Rockefeller, Harry" <Harry dot Rockefeller at flightsafety dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Thu, 4 Apr 2019 17:55:49 +0000
- Subject: RE: emacs-X11 freezes with mouse cut and paste
- References: <fa6ec2233a744738b4efa74af9e9e68c@vsrv060ex01.ssd.fsi.com> <614fbba4-3425-4705-3342-99bbe8684ee0@cornell.edu> <94be9b602dbf4c02b6f7f796895b9475@vsrv060ex01.ssd.fsi.com> <87tvfdd6h5.fsf@Rainer.invalid>
>> It happened again. Attached to PID as shown above. (gdb) list gave same result as above.
>> (gdb) bt
>> #0 0x00000000773bafb1 in ntdll!DbgBreakPoint () from
>> /cygdrive/c/Windows/SYSTEM32/ntdll.dll
>> #1 0x0000000077462e08 in ntdll!DbgUiRemoteBreakin () from
>> /cygdrive/c/Windows/SYSTEM32/ntdll.dll
>> #2 0x00000000772659cd in KERNEL32!BaseThreadInitThunk () from
>> /cygdrive/c/Windows/system32/kernel32.dll
>> #3 0x000000007739a561 in ntdll!RtlUserThreadStart () from
>> /cygdrive/c/Windows/SYSTEM32/ntdll.dll
>> #4 0x0000000000000000 in ?? ()
>> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>>
>> Does this tell me the problem is not Cygwin? Perhaps BLODA or bad hardware, maybe bad mouse?
>Send the Emacs process a USR2 signal (maybe twice). Once Emacs displays a backtrace you can use it again. Usually even pasting with the >mouse works after that.
>Regards,
>Achim.
Kill -s USR2 <PID>
worked. I got the backtrace and the emacs session is responding to keyboard and mouse again. Thanks.
I also used Ken's suggestion sending "thread 1" to gdb and then "bt". It did give much more information
but I don't know if any of it is useful.
--
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