public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Mike <mailbox_home1@yahoo.com>
To: cygwin-xfree@cygwin.com
Subject: Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7
Date: Mon, 24 May 2010 16:30:00 -0000 [thread overview]
Message-ID: <loom.20100524T175249-501@post.gmane.org> (raw)
In-Reply-To: <20100503184556.GA5620@ednor.casa.cgf.cx>
>
> On Mon, May 03, 2010 at 09:37:04PM +0300, Yuval Emek wrote:
> >I'll check it, but I don't think that this is the case because she is
> >experiencing this problem on her private laptop (in my case, it's the
> >company's laptop).
> >
> >Any other suggestions?
>
> Ok, then generalize this further: Since the mailing lists are not filled
> with people reporting these failures, figure out what is similar between
> your office mate and your system.
>
> cgf
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Problem reports: http://cygwin.com/problems.html
> Documentation: http://x.cygwin.com/docs/
> FAQ: http://x.cygwin.com/docs/faq/
>
>
I get the same errors on two machines with the latest cygwin under w7x64. One
machine was built from scratch and has symanetc endpoint, the other one has MS
security essentials. On the latter one I run a previous version of cygwin with
no problems - the problems started after the upgrade. I am using mostly bash and
xemacs - have STATUS_ACCESS_VIOLATION constantly.
412016357 [main] bash 4460 exception::handle: Exception: STATUS_ACCESS_VIOLATION
412017215 [main] bash 4460 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
...
1 [main] xemacs-21.4.22 3664 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
967 [main] xemacs-21.4.22 3664 open_stackdumpfile: Dumping stack trace to
xemacs-21.4.22.exe.stackdump
Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2010-05-24 16:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 15:51 Yuval Emek
2010-05-03 16:37 ` Christopher Faylor
2010-05-03 18:37 ` Yuval Emek
2010-05-03 18:46 ` Christopher Faylor
2010-05-24 16:30 ` Mike [this message]
2010-05-03 18:56 ` Denis Beauchemin
2010-05-03 18:59 ` Christopher Faylor
2010-05-03 19:17 ` Yuval Emek
2010-05-03 19:42 ` Reini Urban
2010-05-03 19:25 ` Christopher Faylor
2010-05-03 20:32 ` Denis Beauchemin
2010-05-22 1:10 ` yuval birnboin
2010-06-09 5:10 ` Michael
2010-06-09 5:31 ` Yaakov (Cygwin/X)
2010-06-10 2:08 ` Michael
2010-07-07 22:35 ` Simon
2010-06-11 19:30 ` Jeff
2010-09-07 3:30 ` Michael
2011-05-15 8:36 ` Whatzit Toya
2011-09-12 14:25 ` Daniel Brockman
2011-09-12 22:10 ` Larry Hall (Cygwin-X)
[not found] ` <4E6E1E6A.5020501@rcf.rhic.bnl.gov>
2013-08-08 14:21 ` unable to get setup.ini Wei Xie
2013-08-08 16:06 ` David Lee Lambert
2011-11-15 19:30 ` frequently getting a STATUS_ACCESS_VIOLATION exception under win7 jenw
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=loom.20100524T175249-501@post.gmane.org \
--to=mailbox_home1@yahoo.com \
--cc=cygwin-xfree@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).