From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
Date: Fri, 02 May 2014 10:50:00 -0000 [thread overview]
Message-ID: <87wqe4cv4x.fsf@Rainer.invalid> (raw)
In-Reply-To: <87fvksekqn.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 02 May 2014 08:51:44 +0200")
Achim Gratz writes:
> Sorry for the long delay. I've now ran the two Emacs versions side by
> side for two days. The original has crashed twice during that time and
> the patched version is still running… so I'd call that a fix. Thanks!
Just as I had sent this mail, the new Emacs also crashed. The backtrace
is likely useless due to the missing symbols (I have it still running in
gdb, though), but it appears to be one of the timer-triggered crashes
(these sometimes only produce a lisp error and sometimes crash Emacs and
I don't think these have anything to do with gnutls). I guess switching
to the 24.4 pre-release is more productive than continuing with trying
to patch the 24.3 version.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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:[~2014-05-02 10:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 17:53 KARR, DAVID
2014-04-14 0:42 ` Ken Brown
2014-04-14 1:47 ` KARR, DAVID
2014-04-14 16:19 ` Ken Brown
2014-04-14 16:28 ` KARR, DAVID
2014-04-14 16:38 ` Ken Brown
2014-04-14 16:43 ` KARR, DAVID
2014-04-14 17:21 ` Achim Gratz
2014-04-14 18:32 ` KARR, DAVID
2014-04-14 18:40 ` Achim Gratz
2014-04-14 18:46 ` Christopher Faylor
2014-04-15 4:08 ` Ken Brown
2014-04-15 7:12 ` Eli Zaretskii
2014-04-15 16:13 ` Ken Brown
2014-04-19 23:38 ` Ken Brown
2014-04-20 1:19 ` KARR, DAVID
2014-04-21 5:14 ` KARR, DAVID
2014-04-21 11:15 ` Ken Brown
2014-04-21 17:26 ` KARR, DAVID
2014-04-21 18:34 ` Ken Brown
2014-04-22 2:21 ` KARR, DAVID
2014-04-23 14:03 ` KARR, DAVID
2014-04-23 15:46 ` Ken Brown
2014-04-23 17:56 ` KARR, DAVID
2014-04-23 18:41 ` Christopher Faylor
2014-04-23 19:11 ` KARR, DAVID
2014-04-24 1:53 ` Christopher Faylor
2014-04-23 23:58 ` David Rothenberger
2014-04-24 12:35 ` Ken Brown
2014-05-02 6:52 ` Achim Gratz
2014-05-02 10:50 ` Achim Gratz [this message]
2014-05-03 2:09 ` Ken Brown
2014-05-08 16:21 ` Achim Gratz
2014-05-03 14:07 ` Achim Gratz
2014-04-15 0:49 ` KARR, DAVID
2014-05-05 21:34 ` KARR, DAVID
2014-05-07 23:42 ` KARR, DAVID
2014-05-08 1:46 ` Ken Brown
2014-05-08 16:03 ` KARR, DAVID
2014-05-09 0:05 ` 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=87wqe4cv4x.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).