From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: latest emacs, cygwin, and constant stackdumps
Date: Tue, 29 Mar 2011 15:35:00 -0000 [thread overview]
Message-ID: <4D91F9AB.6030202@cornell.edu> (raw)
In-Reply-To: <4D91DDEA.6010303@cornell.edu>
On 3/29/2011 9:26 AM, Ken Brown wrote:
> On 3/29/2011 8:48 AM, J. David Boyd wrote:
>>
>> I'm not certain of the exact version of these, but they are the latest,
>> as I upgrade at least once a week.
>>
>> Lately, everytime I do almost anything in emacs, the terminal I started
>> it from shows:
>>
>> [main] emacs-X11 4500 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>> 1149 [main] emacs-X11 4500 open_stackdumpfile: Dumping stack trace to emacs-X11.exe.stackdump
>>
>> Any idea what might be causing this?
>>
>> Everything still works fine, or seems to, but it is rather annoying...
>
> Can you find a reliable way of reproducing this? If so, please send the
> recipe, including all details (what terminal you're using, exactly what
> keys you're pressing in emacs, etc.) Be sure to start emacs with the
> command 'emacs -Q' to eliminate the influence of your customizations.
>
> And please follow the problem-reporting guidelines at
>
> http://cygwin.com/problems.html
>
> including the part about attaching cygcheck output.
>
> Also, it might make sense to update your Cygwin installation first,
> since new versions of cygwin and and xorg-server were just released today.
>
> Finally, please tell me if the problem occurs with both emacs-23.3-1 and
> the test release emacs-23.3-2.
Another thought: Have you tried rebaseall?.
Ken
--
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:[~2011-03-29 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 13:30 J. David Boyd
2011-03-29 13:36 ` Ken Brown
2011-03-29 15:35 ` Ken Brown [this message]
2011-04-13 7:42 ` Dan Tsafrir
2011-04-13 10:40 ` Ken Brown
2011-04-13 16:08 ` Jon TURNEY
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=4D91F9AB.6030202@cornell.edu \
--to=kbrown@cornell.edu \
--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).