On Wed, Aug 11, 2021 at 10:10 PM Mark Geisert wrote:
>
> Hi David,
>
> David Dyck via Cygwin wrote:
> > First, thanks for digging further into this.
> >
> > I'm guessing that I am missing some of the developer pieces that
> > assisted you in deducing from
>
> No problem. I was curious about the
Hi David,
David Dyck via Cygwin wrote:
First, thanks for digging further into this.
I'm guessing that I am missing some of the developer pieces that
assisted you in deducing from
No problem. I was curious about the possible Win 11 Preview connection and
happened to have a bit of free time
First, thanks for digging further into this.
I'm guessing that I am missing some of the developer pieces that
assisted you in deducing from
On Tue, Aug 10, 2021 at 10:28 PM Mark Geisert wrote:
>
> Replying to myself, ahem...
>
> Mark Geisert wrote:
> > You could try downgrading ncurses via
Replying to myself, ahem...
Mark Geisert wrote:
Hi David,
David Dyck via Cygwin wrote:
On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis wrote:
Apparently that Windows Version is for the Windows 11 Preview.
That appears to be an alpha quality product, from bug fix announcements.
I didn't find
On Tue, Aug 10, 2021 at 12:50 PM Mark Geisert wrote:
>
>
> You could try downgrading ncurses via Cygwin setup. Best case: things work.
Best case achieved
Ran setup
this is what it said it would do
Uninstall libncursesw10 6.1-1.20190727 (automatically added)
Uninstall ncurses 6.1-1.20190727
On Tue, 10 Aug 2021 at 13:50, Mark Geisert wrote:
>
> David Dyck via Cygwin wrote:
> > On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis wrote:
Are you running any cygwin services? Be sure to stop them, and all
other cygwin processes before running cygwin setup.
Having any cygwin process running
Hi David,
David Dyck via Cygwin wrote:
On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis wrote:
Apparently that Windows Version is for the Windows 11 Preview.
That appears to be an alpha quality product, from bug fix announcements.
I didn't find anything much useful from MS or articles only
On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis wrote:
> Apparently that Windows Version is for the Windows 11 Preview.
> That appears to be an alpha quality product, from bug fix announcements.
> I didn't find anything much useful from MS or articles only features.
> You might want to reach out
On 2021-08-10 08:20, David Dyck via Cygwin wrote:> On Mon, Aug 9, 2021
at 11:09 PM Brian Inglis wrote:
> Microsoft Windows [Version 10.0.22000.120]
You may also want to check your Windows Preview release docs, and
articles about it, for features such as address changes or randomization
On 2021-08-09 23:16, David Dyck via Cygwin wrote:
On Mon, Aug 9, 2021 at 10:04 PM Brian Inglis wrote:
It's a known problem that after Windows updates, especially Insider,
quarterly, or biannually e.g. [20]20H2 [20]2009, it's often advisable to
rerun Cygwin Setup and allow packages to be
On Mon, Aug 9, 2021 at 10:04 PM Brian Inglis wrote:
> It's a known problem that after Windows updates, especially Insider,
> quarterly, or biannually e.g. [20]20H2 [20]2009, it's often advisable to
> rerun Cygwin Setup and allow packages to be upgraded in case patches are
> made for new
On Mon, Aug 9, 2021 at 10:08 PM Takashi Yano wrote:
>
> On Mon, 9 Aug 2021 21:36:15 -0700
> David Dyck wrote:
> > I've had it running for many years, but recently upgraded to windows 10
> > c:\cygwin64\bin>ver
> >
> > Microsoft Windows [Version 10.0.22000.120]
>
> This does not seem to be a
O WARRANTY, to the extent permitted by law.
>
> here is a sample stackdump
>
> $ wc -l *.stackdump
>25 bash.exe.stackdump
> 9 fish.exe.stackdump
> 9 infocmp.exe.stackdump
>18 less.exe.stackdump
> 9 more.exe.stackdump
>28 python2.7.exe.stackdump
>
On 2021-08-09 22:36, David Dyck via Cygwin wrote:
I'm having trouble getting cygwin bash to start up - I tried older
versions of bash, and I see that other tools are crashing also. I'm
looking for ideas on how to collect the useful information to begin
the path to getting operation of cygwin
On Tue, Feb 25, 2014 at 06:25:18PM +, Shaun Gosse wrote:
Oh, and http://cygwin.com/problems.html suggested running cygcheck, but it's
not found:
-sh-4.1$ cygcheck
-sh: cygcheck: command not found
It's there if you have a shell prompt. You likely just have to
specify the complete path.
You
My previous send didn't go through apparently; needs address obfuscation, now
done.
-Original Message-
From: Shaun Gosse
Sent: Tuesday, February 25, 2014 2:00 PM
To: 'cygwin AT cygwin DOT com'
Subject: RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION)
on default
Apologies for the spam...forgot to reattach the results of the cygcheck when
resending.
-Original Message-
From: Shaun Gosse
Sent: Tuesday, February 25, 2014 3:07 PM
To: 'cygwin AT Cygwin DOT com'
Subject: RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION)
on default
On Thu, Nov 14, 2013 at 10:33:04AM -0500, Chris Betti wrote:
Segmentation fault caused when running this command in a local git
repository. Full permissions are available to the user:
grep -RIin foo .
Segmentation fault (core dumped)
Sorry but I can't duplicate this so I assume it is content
Segmentation fault caused when running this command in a local git
repository. Full permissions are available to the user:
grep -RIin foo .
Segmentation fault (core dumped)
Dump file contains:
Exception: STATUS_ACCESS_VIOLATION at rip=000773B2F42
rax=000600096275 rbx=000600096275 rcx
Brian Inglis Brian.Inglis at SystematicSw.ab.ca writes:
Found problem in man.c line 342 passing NULL manpage_section pointer to
strlen() below.
Patched by upstream in rev 4901:
http://svn.savannah.gnu.org/viewvc?view=revroot=texinforevision=4901
support for MS-Windows screen and keyboard in
On Nov 9 10:42, Brian Inglis wrote:
Brian Inglis Brian.Inglis at SystematicSw.ab.ca writes:
Found problem in man.c line 342 passing NULL manpage_section pointer to
strlen() below.
Patched by upstream in rev 4901:
http://svn.savannah.gnu.org/viewvc?view=revroot=texinforevision=4901
Corinna Vinschen corinna-cygwin at cygwin.com writes:
http://cygwin.com/ml/cygwin-announce/2013-11/msg6.html
http://cygwin.com/ml/cygwin/2013-11/msg00157.html
Corinna
Thanks. Fast work. cygwin64 info now works as expected, so I can stop using
man commands again.
--
Problem
Csaba Raduly rcsaba at gmail.com writes:
cygcheck output appended with usernames Xed:
Note that according to http://cygwin.com/problems.html#cygcheck , you
should send the cygcheck output as an attachment, not paste it into
the body of the message.
Hi Csaba, Reading via RSS feed and posting
Hi Brian,
On Tue, Nov 5, 2013 at 8:27 PM, Brian Inglis wrote:
cygcheck output appended with usernames Xed:
(snip)
Note that according to http://cygwin.com/problems.html#cygcheck , you
should send the cygcheck output as an attachment, not paste it into
the body of the message.
If somebody
Brian Inglis Brian.Inglis at SystematicSw.ab.ca writes:
cygwin64 info.exe consistently dumps when no info file is found - whether or
not there is a man page.
cygwin32 works as always, displaying a man page if found, or status line
message No menu item `' in node `(dir)Top'.
cygcheck
/KERNELBASE.dll
(gdb) cont
Continuing.
0 [main] info 1876 open_stackdumpfile: Dumping stack trace to
info.exe.stackdump
[Inferior 1 (process 1876) exited with code 0105400]
(gdb) q
Stackdumps:
gdb run sntp
Exception: STATUS_ACCESS_VIOLATION at rip=00180168EBD
rax= rbx
Hi,
Often, i have this error using cygwin :
error 1 [main] sh 1964 exception::handle: Exception:
STATUS_ACCESS_VIOLATION,
679 [main] sh 1964 open_stackdumpfile: Dumping stack trace to
sh.exe.stackdump
cygwin is installed on a server Windows 2008.
cygwin receive a ssh instruction from
On 4/16/2013 4:38 PM, Helene LESPES wrote:
Hi,
Often, i have this error using cygwin :
error 1 [main] sh 1964 exception::handle: Exception:
STATUS_ACCESS_VIOLATION,
679 [main] sh 1964 open_stackdumpfile: Dumping stack trace to
sh.exe.stackdump
cygwin is installed on a server Windows 2008
I am using eclipse cdt on Windows 8 and the latest Cygwin gcc release. I
have been barely using any C for awhile, so really it is like I am just
starting. I am trying to do something simple:
int *ptr = malloc(sizeof(*ptr));
int x = 87;
ptr = x;
printf(%d, *ptr);
On Sun, Jan 13, 2013 at 7:55 PM, YZFury yzf...@gmail.com wrote:
int *ptr = malloc(sizeof(*ptr));
int x = 87;
ptr = x;
printf(%d, *ptr);
free(ptr);//it goes wrong here
As you probably know, you can't call free() on a pointer
that didn't come from malloc().
Fire
_
From: Dan Kegel-2 [via Cygwin] ml-node+s1069669n95381...@n5.nabble.com
Sent: Sun Jan 13 23:52:50 EST 2013
To: YZFury yzf...@gmail.com
Subject: Re: Using the free(*ptr) routine and getting an exception, Exception:
STATUS_ACCESS_VIOLATION
\bash.exe --login /cygdrive/c/Backup/syncvia.sh
I get
[exec] C:\Backupc:\cygwin\bin\bash.exe --login
/cygdrive/c/Backup/syncvia.sh
[exec] 0 [main] bash 3468 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
[exec] 774 [main] bash 3468 open_stackdumpfile: Dumping stack
* build script.
E.g. if I try to execute:
c:\cygwin\bin\bash.exe --login /cygdrive/c/Backup/syncvia.sh
I get
[exec] C:\Backupc:\cygwin\bin\bash.exe --login
/cygdrive/c/Backup/syncvia.sh
[exec] 0 [main] bash 3468 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
[exec
Am 07.04.2012 19:38, schrieb Christopher Faylor:
On Sat, Apr 07, 2012 at 10:48:09AM +0200, Andre Loker wrote:
Hello,
On a new system with a clean 1.7.13 installation (CYGWIN_NT-6.1-WOW64
rs200313 1.7.13(0.260/5/3) 2012-04-05 12:43 i686 Cygwin) I'm getting
STATUS_ACCESS_VIOLATIONs whenever I
On Sat, Apr 07, 2012 at 09:49:24PM +0200, Andre Loker wrote:
Am 07.04.2012 19:38, schrieb Christopher Faylor:
On Sat, Apr 07, 2012 at 10:48:09AM +0200, Andre Loker wrote:
Hello,
On a new system with a clean 1.7.13 installation (CYGWIN_NT-6.1-WOW64
rs200313 1.7.13(0.260/5/3) 2012-04-05 12:43
On Nov 30 15:33, Jim Schneider wrote:
I updated today to 1.7.9-1 from an earlier install. Now, bash produces a
series of dozens of exception lines like the following:
214713567 [main] bash 5368 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
214714267 [main] bash 5368
:
STATUS_ACCESS_VIOLATION
214714267 [main] bash 5368 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
The contents of bash.exe.stackdump are:
Exception: STATUS_ACCESS_VIOLATION at eip=6102048B
eax=00C40308 ebx=6124545C ecx=75110F81 edx=003C51F8 esi= edi=0028F9F4
ebp
I updated today to 1.7.9-1 from an earlier install. Now, bash produces a
series of dozens of exception lines like the following:
214713567 [main] bash 5368 exception::handle: Exception: STATUS_ACCESS_VIOLATION
214714267 [main] bash 5368 open_stackdumpfile: Dumping stack trace
On 11/30/2011 9:33 PM, Jim Schneider wrote:
I updated today to 1.7.9-1 from an earlier install. Now, bash produces a
series of dozens of exception lines like the following:
214713567 [main] bash 5368 exception::handle: Exception: STATUS_ACCESS_VIOLATION
214714267 [main] bash 5368
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:
Kris Thielemans-2 wrote:
Hi
I'm running (up-to-date) Cygwin 1.7.9-1 on Windows7 sp1 64-bit.
I recently am getting lots of errors like this
bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION
The messages do not happen all the time (for example, from bash (in minty)
I
--
View this message in context:
http://old.nabble.com/STATUS_ACCESS_VIOLATION-tp32557806p32581457.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
can see that the understanding is in a good shape and light
is at the end of the tunnel.
I'll be happy to wait for a fix in an official version.
Thanks again!
Marc
--
View this message in context:
http://old.nabble.com/STATUS_ACCESS_VIOLATION-tp32557806p32584519.html
Sent from the Cygwin list
PM)
Marc
--
View this message in context:
http://old.nabble.com/STATUS_ACCESS_VIOLATION-tp32557806p32576940.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
proves to be stable and the BLODA list and rebaseall workaround disappear.)
However, STATUS_ACCESS_VIOLATION frequently appears for reason that I do not
count as part of the above, although it is connected.
Some time ago, dll::init() contained
| /* This should be a no-op. Why didn't we just
Marc Girod wrote:
Hello,
I keep my installation up-to-date on a weekly basis, and never fail to
rebaseall/peflagsall as many times as needed to be able to start emacs
in an X session without fork errors. Then I do a perlrebase.
However, I eventually get STATUS_ACCESS_VIOLATION errors
On Sun, Oct 02, 2011 at 03:12:39AM -0700, Marc Girod wrote:
marco atzeri-4 wrote:
My experience is that using the standard problem report improve the
chance to correctly identify the root cause and reduce the number of
guess that everyone could have.
One problem I have is that I use this list
Hello,
I keep my installation up-to-date on a weekly basis, and never fail to
rebaseall/peflagsall as many times as needed to be able to start emacs
in an X session without fork errors. Then I do a perlrebase.
However, I eventually get STATUS_ACCESS_VIOLATION errors, in
various contexts, e.g
STATUS_ACCESS_VIOLATION errors, in
various contexts, e.g. (last now) doing a dired.
I have been keeping the *stackdump files produced, and even logging
their contents for fear they would get overwritten.
I note that the value of eip (instruction pointer register?) reported is
often the same. Here are the data
...
Maybe you are right and I have a *problem* which I ought the *report*.
But that's not exactly the way I was looking at it.
Marc
--
View this message in context:
http://old.nabble.com/STATUS_ACCESS_VIOLATION-tp32557806p32569776.html
Sent from the Cygwin list mailing list archive at Nabble.com
On 9/30/2011 5:33 PM, Marc Girod wrote:
marco atzeri-4 wrote:
Problem reports: http://cygwin.com/problems.html
so at least we have an idea of your system
in addition, have you checked
http://cygwin.com/faq/faq.using.html#faq.using.bloda
Antivirus and driver are the most likely
Hi
I'm running (up-to-date) Cygwin 1.7.9-1 on Windows7 sp1 64-bit.
I recently am getting lots of errors like this
bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION
The messages do not happen all the time (for example, from bash (in minty) I
do a few times ls. After about 4, I get
On 8/14/2011 1:31 PM, David M. Karr wrote:
I'm now in a situation where rxvt and Emacs runs, but the bash that rxvt
runs fails with something like this:
David, try running rebaseall.
--
Larry
_
A: Yes.
Q: Are you sure?
A:
On 8/15/2011 10:01 AM, Larry Hall (Cygwin) wrote:
On 8/14/2011 1:31 PM, David M. Karr wrote:
I'm now in a situation where rxvt and Emacs runs, but the bash that rxvt
runs fails with something like this:
David, try running rebaseall.
I should have known.
Working again. Thanks.
--
Problem
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
Yaakov (Cygwin/X) wrote:
On Mon, 2011-04-11 at 13:44 -0400, Tomas Staig wrote:
First I'll state that this is most probably not BLODA (unless some
default program that comes with W7 provokes it),
FWIW, Windows Defender is a default component of recent versions of
Windows, including
parts of the compilation work ok), at
some point it tries to execute the (compiled during the process) IDL
compiler tao_idl.exe, which randomly (more often than not) ends up in an
STATUS_ACCESS_VIOLATION message and, some of these times with an
additional comment saying preprocessor 'g++' returned
On Mon, 2011-04-11 at 13:44 -0400, Tomas Staig wrote:
First I'll state that this is most probably not BLODA (unless some
default program that comes with W7 provokes it),
FWIW, Windows Defender is a default component of recent versions of
Windows, including Win7, and is BLODA.
Yaakov
--
/bin/rebaseall worked. Great, thanks man!
--
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
Whenever cygwin hasn't been running for awhile, launching it yields a
lot of STATUS_ACCESS_VIOLATION in bash.exe
$ cat bash.exe.stackdump
13779031 [main] bash 4212 exception::handle: Exception: STATUS_ACCESS_VIOLATION
13779775 [main] bash 4212 open_stackdumpfile: Dumping stack trace
On 11/6/2010 4:57 PM, Joshua Hudson wrote:
78995859 [main] bash 996 child_copy: linked dll data write copy failed, 0x33D000
..0x3414A4, done 0, windows pid 996, Win32 error 487
This indicates one of two things:
1. You need to rebase your system. Install the 'rebase' package and
read
Dear All,
I compiled a program under the latest version of Cygwin (1.7.7). But when I run
my executable file, I get a STATUS_ACCESS_VIOLATION exception. I tried peflags
--tsaware=true myprogram.exe and even peflagsall (in ash) but none of them
could solve the problem. Does anybody know how
On 10/19/2010 12:16 PM, Hadi Hadizadeh wrote:
Dear All,
I compiled a program under the latest version of Cygwin (1.7.7). But when I run
my executable file, I get a STATUS_ACCESS_VIOLATION exception.
Are you sure your code isn't buggy? That's usually the sign of a NULL
dereference or other
Hi when I try to run Gvim under X this is the error I am getting. I am
not technically knowledged about these messages, maybe someone can
shed light into this issue.
510575 [main] gvim 1988 exception::handle: Exception: STATUS_ACCESS_VIOLATION
510805 [main] gvim 1988 open_stackdumpfile
Hi,
While trying to run 'gvim', we get the following messages:
**
bash-3.2$ gvim
4 [main] gvim 6964 exception::handle: Exception: STATUS_ACCESS_VIOLATION
1184 [main] gvim 6964 open_stackdumpfile
On 9/14/2010 10:40 AM, טל ח wrote:
4 [main] gvim 7236 C:\cygwin\bin\gvim.exe: *** fatal error -
unable to remap
_\\?\C:\cygwin\lib\gtk-2.0\2.10.0\loaders\cygpixbufloader-xpm.dll to
same address as parent: 0x5D != 0x60 Stack trace:
Try installing the 'rebase' package,
reading
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
.
8 [main] fvwm 3168 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
101981 [main] fvwm 3168 open_stackdumpfile: Dumping stack trace
to fvwm.exe.stackdump
8 [main] xterm 468 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
1591 [main] xterm 468
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
The same kind of problem was reported earlier by Yuval Emek on May 3, 2010.
I am having a number of STATUS_ACCESS_VIOLATION issues, although most of
them are intermittent, which makes me think it is some kind of timing
problem. I am running Cygwin 1.75 under Windows 7 Pro. I changed
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
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
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
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
option)
Here is the stackdump:
Exception: STATUS_ACCESS_VIOLATION at eip=611097F3
eax=4D61696C ebx= ecx= edx=4D61696C esi=0001
edi=4D61696C
ebp=0022B778 esp=0022B774
program=C:\cygwin\tmp\imap-2007e\imapd\imapd.exe, pid 1560, thread main
cs=001B ds=0023 es=0023 fs=003B gs= ss
/system32/Secur32.dll
(0x77fe)
(I am not using the SSL option)
Here is the stackdump:
Exception: STATUS_ACCESS_VIOLATION at eip=611097F3
eax=4D61696C ebx= ecx= edx=4D61696C esi=0001
edi=4D61696C
ebp=0022B778 esp=0022B774
program=C:\cygwin\tmp\imap-2007e\imapd\imapd.exe
cw wrote:
I am trying to compile the latest release of uw-imapd under Cygwin and
Windows XP but the program crash after the first command.
This is with the vanilla source from upstream. I know that it is not
supposed to work very well but yesterday I did the same thing on a
Windows Seven
I am sorry, this was completely my fault.
I made a stupid syntax mistake while changing the source to configure
the program and that was the cause of the problem.
Sorry again.
On Wed, 02 Jun 2010 10:04 -0400, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
On Wed, Jun 02,
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
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
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
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
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
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
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
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
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.
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
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:
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,
On Tue, Apr 20, 2010 at 17:26, Christopher Faylor wrote:
On Tue, Apr 20, 2010 at 09:19:28AM +0300, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
On 4/19/2010 7:44 AM, Yuval Emek wrote:
On Mon,
On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
On 4/19/2010 7:44 AM, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
cgf-use-the-mailinglist-please... wrote:
^
Is it possible that this problem is somehow related to another problem
I'm experiencing, reported in
http://cygwin.com/ml/cygwin/2010-04/msg00797.html ?
On Tue, Apr 20, 2010 at 09:19, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
On Mon, Apr 19, 2010 at 10:48:18AM
On Tue, Apr 20, 2010 at 09:19:28AM +0300, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
On 4/19/2010 7:44 AM, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
On Mon, Apr 19, 2010 at 02:20:48AM +0100, Dave Korn wrote:
On 18/04/2010 23:09, Yuval Emek wrote:
The context of the file xterm.exe.stackdump is:
Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi= edi=0022FA14
ebp=61020A10 esp
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
On Mon, Apr 19, 2010 at 02:20:48AM +0100, Dave Korn wrote:
On 18/04/2010 23:09, Yuval Emek wrote:
The context of the file xterm.exe.stackdump is:
Exception: STATUS_ACCESS_VIOLATION at eip
On 4/19/2010 7:44 AM, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
cgf-use-the-mailinglist-please... wrote:
^
http://cygwin.com/acronyms/#PCYMTNQREAIYR. Feeding spammers just makes
them hungry.
snip
p.envptr is supposed to be filled
On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
On 4/19/2010 7:44 AM, Yuval Emek wrote:
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
cgf-use-the-mailinglist-please... wrote:
^
http://cygwin.com/acronyms/#PCYMTNQREAIYR. Feeding
Recently, when trying to run various programs (e.g., xterm, emacs,
subversion), I often get a message of the following type:
4 [main] xterm 4640 exception::handle: Exception: STATUS_ACCESS_VIOLATION
496 [main] xterm 4640 open_stackdumpfile: Dumping stack trace to
xterm.exe.stackdump
The context
On 18/04/2010 23:09, Yuval Emek wrote:
The context of the file xterm.exe.stackdump is:
Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi= edi=0022FA14
ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4640, thread
1 - 100 of 165 matches
Mail list logo
