public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: emacs-24.3.93-1 [TEST]
Date: Thu, 21 Aug 2014 05:08:00 -0000	[thread overview]
Message-ID: <8761hmbfaf.fsf@Rainer.invalid> (raw)
In-Reply-To: <announce.53F1F088.40706@cornell.edu> (Ken Brown's message of	"Mon, 18 Aug 2014 08:24:40 -0400")

Ken Brown writes:
> This is another pretest of the upcoming emacs-24.4, replacing the
> current pretest (24.3.91-1).  It includes a workaround for the bug
> reported in
>
>   https://cygwin.com/ml/cygwin/2014-07/msg00387.html

I've ran the new test version for a while now, mostly emacs-w32, but
also (not as long or often) emacs-X11 and emacs-nox in mintty (w/ tmux
and screen).  The messages about some locks not behaving correctly and
Emacs after some time either going on anyway or just crashing have not
yet appeared again, so I tentatively conclude these are gone.  I've also
not had strange messages about some errors related to timers, but these
had been so rare anyway that I can't say if they might still be present.

There are still crashes of emacs-w32 that take down Emacs completely
(sometimes with but mostly without it asking for the debugger to be
attached).  So far these have all occured directly in response to
keyboard input (as in the window disappears while the key is still
pressed down).  Let me know if the stackdump would be useful or if I
need to wait out an occasion for when it asks for the debugger to attach
and what to do then.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

--
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

  parent reply	other threads:[~2014-08-21  5:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 12:31 Ken Brown
2014-08-19  9:26 ` Achim Gratz
2014-08-19 14:22   ` Ken Brown
2014-08-21  5:08 ` Achim Gratz [this message]
2014-08-21  6:13   ` Peter Hull
2014-08-21 12:12   ` Achim Gratz
2014-08-21 13:58     ` Ken Brown
2014-08-21 14:06       ` Markus Hoenicka
2014-08-21 14:33         ` Ken Brown
2014-08-21 14:30       ` Achim Gratz
2014-08-21 14:48       ` Eli Zaretskii
2014-09-13 16:18 ` Ken Brown

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=8761hmbfaf.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).