public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Denis Beauchemin <Denis.Beauchemin@USherbrooke.ca>
To: cygwin-xfree@cygwin.com
Subject: Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7
Date: Mon, 03 May 2010 18:56:00 -0000 [thread overview]
Message-ID: <4BDF1C49.6070101@USherbrooke.ca> (raw)
In-Reply-To: <r2r9d1cfe481005030851qb5559440w7318240333478229@mail.gmail.com>
Hello all,
I do get the same error msgs. Setup: Cygwin/X 1.7.6 (build 2010-03-22),
win7-64, McAfee, etc.
Denis
Le 2010-05-03 11:51, Yuval Emek a écrit :
> A very annoying situation: I'm getting a STATUS_ACCESS_VIOLATION
> exception in about 2 out of 3 operations performed under cygwin/x. An
> operation in this context can be starting an x application (e.g.,
> xterm) or running some command from within emacs (e.g., diff or
> latex).
>
> In attempt to isolate the problem, I reinstalled cygwin from scratch
> using the default settings of setup.exe + xorg-server, xinit,
> xorg-docs, and X-start-menu-icons.
> Next, I open a cygwin bash window and then invoke startxwin.exe .
> The x-server is invoked but an xterm window does not open and the
> following message appears:
>
> ***message begins***
> 4 [main] xterm 7156 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> 1449 [main] xterm 7156 open_stackdumpfile: Dumping stack trace to xterm.exe.s
> tackdump
> 4 [main] xterm 7996 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> 1356 [main] xterm 7996 open_stackdumpfile: Dumping stack trace to xterm.exe.s
> tackdump
> 4 [main] xterm 5268 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> 647 [main] xterm 5268 open_stackdumpfile: Dumping stack trace to xterm.exe.s
> tackdump
> 5 [main] xterm 4316 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> 739 [main] xterm 4316 open_stackdumpfile: Dumping stack trace to xterm.exe.s
> tackdump
> 2 [main] xterm 2752 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> 1123 [main] xterm 2752 open_stackdumpfile: Dumping stack trace to xterm.exe.s
> tackdump
> 5 [main] xterm 3220 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> 1260 [main] xterm 3220 open_stackdumpfile: Dumping stack trace to xterm.exe.s
> tackdump
> 6 [main] xterm 6752 fork: child -1 - died waiting for longjmp before initi
> alization, retry 0, exit code 0x600, errno 11
> xterm: Error 29, errno 11: Resource temporarily unavailable
> Reason: spawn: fork() failed
> ***message ends***
>
> The content of the resulting xterm.exe.stackdump file:
>
> ***content begins***
> Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
> eax=00C500F8 ebx=612294A4 ecx=755F783F edx=002620F0 esi=00000000 edi=0022FA14
> ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 3220, thread main
>
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame Function Args
> End of stack trace
> ***content ends***
>
> This phenomenon (or a similar one where I'm getting only 1 or two
> lines of the exception and xterm does open) is very common: it happens
> in about 2 out of 3 startxwin.exe invocation attempts. The same thing
> happens when I'm trying to open a new xterm window from an existing
> one.
>
> I'm using Windows 7 (32 bits). This is probably a relevant info as my
> old laptop (with Windows XP) works fine (once again with a fresh
> installation of cygwin + cygwin/x).
>
> I'm somewhat surprised that this problem was not reported before since
> I know that my office mate suffers from it as well (she is also using
> Windows 7 32 bits).
>
> I've already tried to discuss this problem in the cygwin mailing list
> (see http://cygwin.com/ml/cygwin/2010-04/msg00740.html) without a
> positive resolution. Thinking about it some more, I now understand
> that this problem occurs only under x, so I hope that this is the
> right mailing list.
>
> Any suggestions?
>
> The output of cygcheck -s -v -r and the content of /var/log/XWin.0.log
> are attached.
>
>
>
> --
> 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/
--
_
°v° Denis Beauchemin, analyste
/(_)\ Université de Sherbrooke, S.T.I.
^ ^ T: 819.821.8000x62252 F: 819.821.8045
--
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-03 18:56 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
2010-05-03 18:56 ` Denis Beauchemin [this message]
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=4BDF1C49.6070101@USherbrooke.ca \
--to=denis.beauchemin@usherbrooke.ca \
--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).