From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4113 invoked by alias); 10 Jun 2014 23:35:23 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 4100 invoked by uid 89); 10 Jun 2014 23:35:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: smtprelay04.ispgateway.de Received: from smtprelay04.ispgateway.de (HELO smtprelay04.ispgateway.de) (80.67.31.27) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 10 Jun 2014 23:35:20 +0000 Received: from [77.2.42.103] (helo=wombat.mininet) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1WuVZT-00010G-1C for cygwin@cygwin.com; Wed, 11 Jun 2014 01:35:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <21399.38522.378111.667474@wombat.mininet> Date: Tue, 10 Jun 2014 23:35:00 -0000 To: cygwin@cygwin.com Subject: Re: emacs oddity In-Reply-To: <227438ea5579471db71c9587ea622d4e@mhoenicka.de> References: <537bec06.6926ec0a.5737.68db@mx.google.com> <537C04A0.60409@cornell.edu> <537C922F.7090809@cornell.edu> <227438ea5579471db71c9587ea622d4e@mhoenicka.de> From: markus.hoenicka@mhoenicka.de X-Df-Sender: NDcyNTgy X-IsSubscribed: yes X-SW-Source: 2014-06/txt/msg00134.txt.bz2 Markus Hoenicka writes: > Am 2014-05-21 13:46, schrieb Ken Brown: > > On 5/21/2014 3:13 AM, Markus Hoenicka wrote: > >> At 2014-05-21 03:42, Ken Brown was heard to say: > >>> On 5/20/2014 7:57 PM, Max Polk wrote: > >>>> I've been noticing the background timer giving odd messages from > >>>> emacs-w32 once in a while such as the following when not touching=20 > >>>> the > >>>> keyboard and the editor is idle.: > >>>>=20 > >>>> seconds-to-time: Arithmetic range error: "round", -0.0e+NaN > >>>> seconds-to-time: Arithmetic range error: "round", 0.0 > >>>>=20 > >>>> The stack dump of a recent emacs crash report on this list seemed to > >>>> be in background timer code. Maybe we found something. > >>>=20 > >>> Have you tried the test release > >>> (https://cygwin.com/ml/cygwin/2014-05/msg00047.html)? > >>>=20 > >>=20 > >> Hi, > >>=20 > >> I haven't followed this thread in all its gory details, but I recall > >> that only emacs-w32 was reported to have problems. I have noticed=20 > >> random > >> crashes and weird messages without prior user actions in emacs-x11=20 > >> since > >> I moved from WinXP + Cygwin x86 to Win7 + Cygwin x86_64 a few weeks=20 > >> ago. > >> None of these problems ever occurred on either FreeBSD (amd64, Emacs= =20 > >> 24) > >> or Debian (amd64, Emacs 23). I just thought I'd mention this because= =20 > >> the > >> problem does not seem to be limited to the -w32 build of Emacs. I've > >> preserved the odd messages on three separate occasions: > >>=20 > >> Args out of range: [t 21335 39727 373923 0.5=20 > >> blink-cursor-timer-function > >> nil nil 100000], 4 > >>=20 > >> Invalid function: #[(timer) "^H >^H > >>> ^[\211^203^Q^@=C5^H \"^Q^K\203^Z^@=C5^H > >> \"^R^L\206^_^@^K*\207" [timer timer-list timer-idle-list cell2 cell1 > >> delq] 4 2245674] > >>=20 > >> timer-relative-time: Wrong type argument: vectorp, [t1 time high low > >> micro pico nil 3 0 2 ...] > >>=20 > >> All of them indicate timer related problems as Max pointed out. I do= =20 > >> not > >> have meaningful backtraces of the crashes at this time because the > >> installed emacs-x11 seems to lack debug symbols. > >=20 > > You have to install emacs-debuginfo in order to get the symbols. > >=20 >=20 > Thanks, I've installed it now just in case. Until now, no crashes or=20 > weird messages with emacs-X11-24.3.90-1 yet... >=20 > regards, > Markus >=20 Hi, I've been testing emacs-X11-24.3.90-1 for more than two weeks now, and this is what happened: - a few hours after I claimed that there were no problems with this version yet (see above), Emacs crashed again. - I used to start Emacs from gdb for about two weeks, hoping to catch it red-handed. No problems occurred - I reverted to starting Emacs as I had done for years (through startxwin), but I've set up the CYGWIN environment variable to create true core dumps. A couple of days later Emacs crashed again and left a core dump. I've sent that along with a problem description to bug-gnu-emacs AT gnu.org: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D17753 This basically means that the current test release is a major improvement although it did not eliminate crashes altogether. As I do not have any core dumps of the previous Emacs version, I can't even tell whether or not the same bugs are involved. regards, Markus --=20 Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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