From: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: emacs-X11 freezes with mouse cut and paste
Date: Thu, 04 Apr 2019 17:55:00 -0000 [thread overview]
Message-ID: <1ba1dcab619949cf84a18029405bd5c6@vsrv060ex01.ssd.fsi.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2019-04-04 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 14:41 Rockefeller, Harry
2019-03-27 18:33 ` Ken Brown
2019-04-04 16:25 ` Rockefeller, Harry
2019-04-04 17:28 ` Ken Brown
2019-04-04 18:31 ` Rockefeller, Harry
2019-04-04 17:29 ` Achim Gratz
2019-04-04 17:55 ` Rockefeller, Harry [this message]
2019-04-04 18:07 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ba1dcab619949cf84a18029405bd5c6@vsrv060ex01.ssd.fsi.com \
--to=harry.rockefeller@flightsafety.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).