From: "KARR, DAVID" <dk068x@att.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Fatal error from Cygwin emacs-w32 every day or so
Date: Wed, 07 May 2014 23:42:00 -0000 [thread overview]
Message-ID: <B8D164BED956C5439875951895CB4B222663A4D5@CAFRFD1MSGUSRIA.ITServices.sbc.com> (raw)
In-Reply-To: <B8D164BED956C5439875951895CB4B2226630D4A@CAFRFD1MSGUSRIG.ITServices.sbc.com>
> -----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 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?
>
> I installed the test 24.3.90.1 version, and it hasn't crashed once (yet).
Since I reported this, I've seen it crash several times now, but it doesn't give the usual "Debug?" dialog, it just goes away. It's died several times today. I'll start running it from gdb to get a stacktrace.
--
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-07 23:42 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
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 [this message]
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=B8D164BED956C5439875951895CB4B222663A4D5@CAFRFD1MSGUSRIA.ITServices.sbc.com \
--to=dk068x@att.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).