Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[jenw]

Thank you, Whatzit Toya, your solution compatibility mode/run as admin solution
worked like a charm for me!
-jw





--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Whatzit Toya]

I was having this same issue running WIN7 x64, cygwin1.dll version 1.7.9, and 
no 
Security Essentials or any other a/v software.

This is how I fixed the issue:

I went into my cygwin installation folder (C:\cygwin\bin), right clicked on 
sh.exe, selected Properties, selected the Compatibility tab, and checked 
Run this program as an administrator.

I did the same thing for bash.exe.

Now it works beautifully without any error messages.

Hope this helps.

PS On sh.exe I also have it running in compatibility mode for Win XP SP2 but 
I 
don't think it is necessary.


--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Michael]

I was having this same issue.  Cygwin Xserver was working properly under Win 
XP, but the fork failure began occuring when I migrated to Win 7 Home Premium 
32-bit.  My issue was Microsoft Security Essentials was set to default which 
allows it to real time scan all files/directories/real-time processes.  If you 
are also running this, I guarantee it is your problem (or at least one of 
them).

To resolve, open Security Essentials and navigate to the settings tab.  Under 
the Excluded files  locations menu, add the cygwin root directory 
(C:\cygwin\ if you used the default install config).  Under excluded 
processes, add startx.exe, startxwin.exe, xterm.exe, and Cygwin.bat.  These 
files will all be in the C:\cygwin\ and C:\cygwin\bin\ directories.

Save the changes to the firewall and give it a shot.



--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Simon]

Michael chaozhan at hotmail.com writes:
 
 Hello,
 
 I got the same problem.
 
 My settings:
 
 Windows 7 64 bit Home Premium
 CYGWIN_NT-6.1-WOW64 my_machine 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin
 
 And I use cygwin 1.7.5 on windows XP has NO problem at all.
 
 But after I completed June 09, 2010 windows updates for windows 7, this 
problem 
 is gone.
 
 I am not sure if this is windows problem or cygwin/X problem.
 
 Any input are welcom!
 
 Michael
 
 --
 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've been having this problem for a number of months too.

I just installed the font-isas-misc, font-jis-misc and font-daewoo-misc 
packages to get around some missing charsets in string to fontset conversion 
warnings and so far I haven't had 1 crash.  Also xterm seems to come up much 
more quickly.

A few other things were updated when I put the fonts in so not positive it was 
the fonts that fixed the issue.




--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Jeff]

We are having the same issue using Cygwin 1.7.5 under Windows 7.I can not 
find an exact pattern but I'd estimate that the xterm windows works about 70% 
of the time.When we get the xterm STATUS_ACCESS_VIOLATION the xterm 
sometimes still comes up and other times no luck.   
When it dies completely it ends with;

[main] xterm 3376 fork: child -1 - died waiting for longjmp before 
initialization, retry 0, exit code 0x100, errno 11
xterm: Error 29, errno 11: Resource temporarily unavailable
Reason: spawn: fork() failed

I'm still searching for a solution.  If I see something, I'll post it.

Jeff


--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Michael]

Hello,

I got the same problem.

My settings:

Windows 7 64 bit Home Premium
CYGWIN_NT-6.1-WOW64 my_machine 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin

And I use cygwin 1.7.5 on windows XP has NO problem at all.

But after I completed June 09, 2010 windows updates for windows 7, this problem 
is gone.

I am not sure if this is windows problem or cygwin/X problem.

Any input are welcom!

Michael



--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Michael]

Yuval Emek yuval.emek at gmail.com writes:

 
 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= 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= 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.
 
 Attachment (XWin.0.log): application/octet-stream, 4224 bytes
 Attachment (xterm.exe.stackdump): application/octet-stream, 321 bytes
 
 --
 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 got the same problem on windows 7 64 bit home premium edition with Cygwin 
1.7.5

And it is no problem on windows XP with Cygwin 1.7.5

$   2 [main] xterm 4552 exception::handle: Exception: STATUS_ACCESS_VIOLATIO
N
   1665 [main] xterm 4552 open_stackdumpfile: Dumping stack trace to xterm.exe.s
tackdump
  2 [main] xterm 5260 exception::handle: Exception: STATUS_ACCESS_VIOLATION
   1220 [main] xterm 5260 open_stackdumpfile: Dumping stack trace to xterm.exe.s
tackdump
  2 [main] xterm 2324 exception::handle: Exception: STATUS_ACCESS_VIOLATION
   1149 [main] xterm 2324 open_stackdumpfile: Dumping stack trace to xterm.exe.s
tackdump
  2 [main] xterm 4196 exception::handle: Exception: STATUS_ACCESS_VIOLATION
   1154 [main] xterm 4196 open_stackdumpfile: Dumping stack trace to xterm.exe.s
tackdump
  2 [main] xterm 5112 exception::handle: Exception: STATUS_ACCESS_VIOLATION
   1696 [main] xterm 5112 open_stackdumpfile: Dumping stack trace to xterm.exe.s
tackdump
  2 [main] xterm 2484 exception::handle: Exception: STATUS_ACCESS_VIOLATION
   1660 [main] xterm 2484 open_stackdumpfile: Dumping stack trace to xterm.exe.s
tackdump
  2 [main] xterm 536 fork: 

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Yaakov (Cygwin/X)]

On Wed, 2010-06-09 at 05:07 +, Michael wrote:
   2 [main] xterm 2484 exception::handle: Exception:
 STATUS_ACCESS_VIOLATION
1660 [main] xterm 2484 open_stackdumpfile: Dumping stack trace to
 xterm.exe.stackdump
   2 [main] xterm 536 fork: child -1 - died waiting for longjmp
 before initialization, retry 0, exit code 0x600, errno 11
 xterm: Error 29, errno 11: Resource temporarily unavailable
 Reason: spawn: fork() failed 
 
 Please provide solution if someone happened to know.

1) BLODA
2) rebaseall


Yaakov
Cygwin/X



--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Mike]

 
 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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[yuval birnboin]

Denis Beauchemin Denis.Beauchemin at USherbrooke.ca writes:

 
 
 Le 2010-05-03 15:25, Christopher Faylor a écrit :
  On Mon, May 03, 2010 at 02:59:22PM -0400, Christopher Faylor wrote:
 
  On Mon, May 03, 2010 at 02:56:09PM -0400, Denis Beauchemin wrote:
   
  Hello all,
 
  I do get the same error msgs. Setup: Cygwin/X 1.7.6 (build 2010-03-22),
  win7-64, McAfee, etc.
 
  McAfee, etc. would probably be a problem.
   
  Another thing to try would be rebaseall if you haven't done so already.
 
  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 just rebaseall. So far so good.
 
 Denis
 

I have been getting a status_access_violation often on x11 related processes
with cygwin1.7, win7-64, McAfee anti virus. An interesting similarity between my
experience and other posts here is that I have Hebrew enabled on my windows
machine. Could this problem related to some locale or language setting imported
from the window environment?

Particularly, top.exe sometimes fails when running from xterm or the dos
terminal (Cygwin Bash Shell; cygwin.bat) as long as xwin is on. Once it fails it
persistently fails. If I close xwin, top works on the cygwin.bat dos terminal
consistently.

I have 'rebaseall'ed - it does not help.

Yuval




--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Christopher Faylor]

On Mon, May 03, 2010 at 06:51:35PM +0300, Yuval Emek wrote:
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).

Since you and an office mate are both having the problem it would point
to some sort of BLODA problem.  Check for resident applications like
virus managers, firewalls, etc.

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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Yuval Emek]

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?

On Mon, May 3, 2010 at 19:37, Christopher Faylor wrote:

 On Mon, May 03, 2010 at 06:51:35PM +0300, Yuval Emek wrote:
 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).

 Since you and an office mate are both having the problem it would point
 to some sort of BLODA problem.  Check for resident applications like
 virus managers, firewalls, etc.

 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/


--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Christopher Faylor]

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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Denis Beauchemin]

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= 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= 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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Christopher Faylor]

On Mon, May 03, 2010 at 02:56:09PM -0400, Denis Beauchemin wrote:
Hello all,

I do get the same error msgs. Setup: Cygwin/X 1.7.6 (build 2010-03-22), 
win7-64, McAfee, etc.

McAfee, etc. would probably be a problem.

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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Yuval Emek]

I'm not using McAfee and in my case it's win7-32.

On Mon, May 3, 2010 at 21:59, Christopher Faylor  wrote:
 On Mon, May 03, 2010 at 02:56:09PM -0400, Denis Beauchemin wrote:
Hello all,

I do get the same error msgs. Setup: Cygwin/X 1.7.6 (build 2010-03-22),
win7-64, McAfee, etc.

 McAfee, etc. would probably be a problem.

 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/



--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Christopher Faylor]

On Mon, May 03, 2010 at 02:59:22PM -0400, Christopher Faylor wrote:
On Mon, May 03, 2010 at 02:56:09PM -0400, Denis Beauchemin wrote:
Hello all,

I do get the same error msgs. Setup: Cygwin/X 1.7.6 (build 2010-03-22), 
win7-64, McAfee, etc.

McAfee, etc. would probably be a problem.

Another thing to try would be rebaseall if you haven't done so already.

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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Reini Urban]

2010/5/3 Yuval Emek:
 I'm not using McAfee and in my case it's win7-32.

Just for the records:
I'm using McAfee and all win7 security settings (DEP, UAC),
no admin rights, and it still works okay.

Just rebasing my various perls drives me crazy.
-- 
Reini

--
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/

Re: frequently getting a STATUS_ACCESS_VIOLATION exception under win7

[Denis Beauchemin]

Le 2010-05-03 15:25, Christopher Faylor a écrit :

On Mon, May 03, 2010 at 02:59:22PM -0400, Christopher Faylor wrote:
   

On Mon, May 03, 2010 at 02:56:09PM -0400, Denis Beauchemin wrote:
 

Hello all,

I do get the same error msgs. Setup: Cygwin/X 1.7.6 (build 2010-03-22),
win7-64, McAfee, etc.
   

McAfee, etc. would probably be a problem.
 

Another thing to try would be rebaseall if you haven't done so already.

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 just rebaseall. So far so good.

Denis

--
   _
  °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/