-Original Message-
On 5/7/2014 7:42 PM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Monday, May 05, 2014 2:34 PM
-Original Message-
Of KARR, DAVID
Sent: Sunday, April 13, 2014 10:53 AM
I recently installed 1.7.29 on a new Win7/64 laptop.
Ken Brown writes:
I agree. I'll do that soon.
Thanks Ken. Due to several updates that required reboots I haven't
really been able to run an Emacs instance for as long as I would have
liked, but so far I haven't seen any error or crash.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron
On 5/8/2014 12:03 PM, KARR, DAVID wrote:
-Original Message-
On 5/7/2014 7:42 PM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Monday, May 05, 2014 2:34 PM
-Original Message-
Of KARR, DAVID
Sent: Sunday, April 13, 2014 10:53 AM
I recently installed 1.7.29
-Original Message-
Of KARR, DAVID
Sent: Monday, May 05, 2014 2:34 PM
-Original Message-
Of KARR, DAVID
Sent: Sunday, April 13, 2014 10:53 AM
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so, I
get a fatal error dialog from emacs-w32. It asks
On 5/7/2014 7:42 PM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Monday, May 05, 2014 2:34 PM
-Original Message-
Of KARR, DAVID
Sent: Sunday, April 13, 2014 10:53 AM
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so, I
get a fatal error
-Original Message-
Of KARR, DAVID
Sent: Sunday, April 13, 2014 10:53 AM
Subject: Fatal error from Cygwin emacs-w32 every day or so
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so, I
get a fatal error dialog from emacs-w32. It asks me if I want to debug
Achim Gratz writes:
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've just had one of these timer-triggered elisp errors in the 32bit
version of emacs-w32
Ken Brown writes:
I've rebuilt emacs-24.3 with the gnutls fix. David and Achim (and
anyone else who's been experiencing these crashes), please try the
following binary and let me know if it solves the problem:
http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
You might have to do
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.
On 5/2/2014 6:50 AM, Achim Gratz wrote:
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
On 4/23/2014 7:56 PM, David Rothenberger wrote:
Ken Brown wrote:
I've rebuilt emacs-24.3 with the gnutls fix. David and Achim (and
anyone else who's been experiencing these crashes), please try the
following binary and let me know if it solves the problem:
-Original Message-
Of KARR, DAVID
Sent: Monday, April 21, 2014 7:21 PM
Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
*** Security Advisory: This Message Originated Outside of ATT ***.
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information
On 4/23/2014 10:03 AM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Monday, April 21, 2014 7:21 PM
Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
*** Security Advisory: This Message Originated Outside of ATT ***.
Reference http://cso.att.com/EmailSecurity
-Original Message-
Of Ken Brown
Sent: Wednesday, April 23, 2014 8:46 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/23/2014 10:03 AM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Monday, April 21, 2014 7:21 PM
Subject: RE: Fatal
On Wed, Apr 23, 2014 at 05:56:16PM +, KARR, DAVID wrote:
(I really do dislike the spam filter on this list. Failing because of
cygwin at cygwin.com in the body is really annoying.)
If you were replying to email rather than forwarding it you wouldn't
have an issue. We don't need to see the
-Original Message-
Of Christopher Faylor
Sent: Wednesday, April 23, 2014 11:42 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On Wed, Apr 23, 2014 at 05:56:16PM +, KARR, DAVID wrote:
(I really do dislike the spam filter on this list. Failing because
Ken Brown wrote:
I've rebuilt emacs-24.3 with the gnutls fix. David and Achim (and
anyone else who's been experiencing these crashes), please try the
following binary and let me know if it solves the problem:
http://sanibeltranquility.com/cygwin/emacs-w32.exe.xz
I had been
On Wed, Apr 23, 2014 at 07:11:02PM +, KARR, DAVID wrote:
-Original Message-
Of Christopher Faylor
Sent: Wednesday, April 23, 2014 11:42 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On Wed, Apr 23, 2014 at 05:56:16PM +, KARR, DAVID wrote:
(I really do
On 4/21/2014 1:14 AM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Saturday, April 19, 2014 6:19 PM
Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
-Original Message-
Of Ken Brown
Sent: Saturday, April 19, 2014 4:38 PM
Subject: Re: Fatal error from
-Original Message-
Of Ken Brown
Sent: Monday, April 21, 2014 4:16 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/21/2014 1:14 AM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Saturday, April 19, 2014 6:19 PM
Subject: RE: Fatal
On 4/21/2014 1:25 PM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Monday, April 21, 2014 4:16 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/21/2014 1:14 AM, KARR, DAVID wrote:
-Original Message-
Of KARR, DAVID
Sent: Saturday, April 19, 2014
-Original Message-
Of Ken Brown
Sent: Monday, April 21, 2014 11:34 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/21/2014 1:25 PM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Monday, April 21, 2014 4:16 AM
Subject: Re: Fatal error
-Original Message-
Of KARR, DAVID
Sent: Saturday, April 19, 2014 6:19 PM
Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
-Original Message-
Of Ken Brown
Sent: Saturday, April 19, 2014 4:38 PM
Subject: Re: Fatal error from Cygwin emacs-w32 every day
On 4/15/2014 12:13 PM, Ken Brown wrote:
On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
Date: Mon, 14 Apr 2014 21:08:15 -0700
From: Ken Brown
I just saw it die, and this is the bt I get:
Program received signal SIGSEGV, Segmentation fault.
0x000100551354 in wait_reading_process_output (
-Original Message-
Of Ken Brown
Sent: Saturday, April 19, 2014 4:38 PM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/15/2014 12:13 PM, Ken Brown wrote:
On 4/15/2014 12:12 AM, Eli Zaretskii wrote:
Date: Mon, 14 Apr 2014 21:08:15 -0700
From: Ken Brown
I
Date: Mon, 14 Apr 2014 21:08:15 -0700
From: Ken Brown kbr...@cornell.edu
I just saw it die, and this is the bt I get:
Program received signal SIGSEGV, Segmentation fault.
0x000100551354 in wait_reading_process_output (
time_limit=time_limit@entry=0, nsecs=nsecs@entry=0,
On 4/13/2014 6:46 PM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Sunday, April 13, 2014 5:43 PM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/13/2014 10:53 AM, KARR, DAVID wrote:
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so
-Original Message-
Of Ken Brown
Sent: Monday, April 14, 2014 9:19 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/13/2014 6:46 PM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Sunday, April 13, 2014 5:43 PM
Subject: Re: Fatal error
On 4/14/2014 9:28 AM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Monday, April 14, 2014 9:19 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/13/2014 6:46 PM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Sunday, April 13, 2014 5
-Original Message-
Of Ken Brown
Sent: Monday, April 14, 2014 9:39 AM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/14/2014 9:28 AM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Monday, April 14, 2014 9:19 AM
Subject: Re: Fatal error
Ken Brown writes:
You might have to run emacs under gdb and put a breakpoint at
emacs_abort in order to get a useful backtrace. But I'm not sure it's
worth putting a lot of effort into debugging emacs-24.3 at this point,
because emacs-24.4 is already in its pretest phase. I'm traveling
-Original Message-
Of Ken Brown
Sent: Sunday, April 13, 2014 5:43 PM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/13/2014 10:53 AM, KARR, DAVID wrote:
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so, I
get a fatal error dialog from
KARR, DAVID writes:
I just saw it die, and this is the bt I get:
Try thread apply all bt.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
Problem
On Mon, Apr 14, 2014 at 08:39:54PM +0200, Achim Gratz wrote:
KARR, DAVID writes:
I just saw it die, and this is the bt I get:
Try thread apply all bt.
gdb should have stopped in the offending thread. Given where
it stopped, it looks like the culprit is wait_proc not being
a valid pointer.
cgf
-Original Message-
From: KARR, DAVID
Sent: Monday, April 14, 2014 11:24 AM
Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
-Original Message-
Of Ken Brown
Sent: Sunday, April 13, 2014 5:43 PM
Subject: Re: Fatal error from Cygwin emacs-w32 every day
On 4/14/2014 11:31 AM, KARR, DAVID wrote:
-Original Message-
Of Ken Brown
Sent: Sunday, April 13, 2014 5:43 PM
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
On 4/13/2014 10:53 AM, KARR, DAVID wrote:
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so, I get a
fatal error dialog from emacs-w32. It asks me if I want to debug it, but I'm
not sure what info I could pull from gdb that would be useful.
Is this a known problem?
Is there any useful information I could provide?
On 4/13/2014 10:53 AM, KARR, DAVID wrote:
I recently installed 1.7.29 on a new Win7/64 laptop. Every day or so, I get a
fatal error dialog from emacs-w32. It asks me if I want to debug it, but I'm
not sure what info I could pull from gdb that would be useful.
A gdb backtrace might or might
38 matches
Mail list logo
