Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 p

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 t

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 Cy

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 an

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 (a

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 wh

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 featur

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 fo

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 (e.

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 upgrade

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 releases,

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 versio

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

> There is NO 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.sta

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

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 res

RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION) on default install with Cygwin 2.831 (64bit) on Windows 7 (64bit)

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)

RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION) on default install with Cygwin 2.831 (64bit) on Windows 7 (64bit)

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_VIOLATI

Re: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION) on default install with Cygwin 2.831 (64bit) on Windows 7 (64bit)

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. Y

Re: Recursive, case insensitive grep (2.14-1 x86-64 MS Windows) causes Exception: STATUS_ACCESS_VIOLATION at rip=000773B2F42

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 con

Recursive, case insensitive grep (2.14-1 x86-64 MS Windows) causes Exception: STATUS_ACCESS_VIOLATION at rip=000773B2F42

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

Re: cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found

Corinna Vinschen 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 reports: http:

Re: cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found

On Nov 9 10:42, Brian Inglis wrote: > Brian Inglis 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=rev&root=texinfo&revision=4901 > support f

Re: cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found

Brian Inglis 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=rev&root=texinfo&revision=4901 support for MS-Windows screen and keyboard in Info, from eliz

Re: cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found

Csaba Raduly 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 via

Re: cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found

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 wan

Re: cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found

Brian Inglis 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 output ap

cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found

/cygdrive/c/Windows/system32/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=

Re: error STATUS_ACCESS_VIOLATION

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

error STATUS_ACCESS_VIOLATION

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 a

Re: Using the free(*ptr) routine and getting an exception, "Exception: STATUS_ACCESS_VIOLATION"

indle Fire _ From: "Dan Kegel-2 [via Cygwin]" Sent: Sun Jan 13 23:52:50 EST 2013 To: YZFury Subject: Re: Using the free(*ptr) routine and getting an exception, "Exception: STATUS_ACCESS_VIOLATION" On Sun, Jan 13, 2013 at

Re: Using the free(*ptr) routine and getting an exception, "Exception: STATUS_ACCESS_VIOLATION"

On Sun, Jan 13, 2013 at 7:55 PM, YZFury 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(). ptr's first

Using the free(*ptr) routine and getting an exception, "Exception: STATUS_ACCESS_VIOLATION"

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);

Re: [1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

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

Re: [1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

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 try

Re: [1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

0 [main] bash 3468 exception::handle: Exception: >STATUS_ACCESS_VIOLATION > [exec] 774 [main] bash 3468 open_stackdumpfile: Dumping stack >trace to bash.exe.stackdump > >Here's the stackdump file: >Exception: STATUS_ACCESS_VIOLATION at eip=61029E40 >eax= ebx=0028ABCC e

[1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts

n\bin\bash.exe --login /cygdrive/c/Backup/syncvia.sh I get [exec] C:\Backup>c:\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: Dumpi

Re: 1.7.9-1 dll::init() still causing STATUS_ACCESS_VIOLATION errors

bash 5368 exception::handle: Exception: >> 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 ei

Re: 1.7.9-1 dll::init() still causing STATUS_ACCESS_VIOLATION errors

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

Re: 1.7.9-1 dll::init() still causing STATUS_ACCESS_VIOLATION errors

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

1.7.9-1 dll::init() still causing STATUS_ACCESS_VIOLATION errors

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 to

Re: bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION

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 t

Re: STATUS_ACCESS_VIOLATION

compare fixes. I 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 f

Re: STATUS_ACCESS_VIOLATION

fying the problem properly. To test the nabble attachments, I send a body of nabble delay mail. http://old.nabble.com/file/p32581457/nabble_delay.txt nabble_delay.txt -- View this message in context: http://old.nabble.com/STATUS_ACCESS_VIOLATION-tp32557806p32581457.html Sent from the C

Re: STATUS_ACCESS_VIOLATION

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 us

Re: STATUS_ACCESS_VIOLATION

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

Re: STATUS_ACCESS_VIOLATION

it is really advisable to try recent snapshot. (Personally, I will stay with my own fixes of fork, until the new code 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

Re: STATUS_ACCESS_VIOLATION

appear here (sent Sat, Oct 1, 2011 at 12:45 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:

Re: STATUS_ACCESS_VIOLATION

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 culprit

Re: STATUS_ACCESS_VIOLATION

its. > Yes, I know both pages... 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 Cyg

Re: STATUS_ACCESS_VIOLATION

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 for

STATUS_ACCESS_VIOLATION

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

bash 2112 exception::handle: Exception: STATUS_ACCESS_VIOLATION

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,

Re: rxvt & emacs runs, but bash and others fail with STATUS_ACCESS_VIOLATION

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 r

Re: rxvt & emacs runs, but bash and others fail with STATUS_ACCESS_VIOLATION

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

Re: Windows7 STATUS_ACCESS_VIOLATION and gcc/g++ linking problems

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 Win7

Re: Windows7 STATUS_ACCESS_VIOLATION and gcc/g++ linking problems

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

Windows7 STATUS_ACCESS_VIOLATION and gcc/g++ linking problems

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

RE: STATUS_ACCESS_VIOLATION

/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

Re: STATUS_ACCESS_VIOLATION

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 th

STATUS_ACCESS_VIOLATION

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 tra

Re: peflags and STATUS_ACCESS_VIOLATION

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 dereferenc

peflags and STATUS_ACCESS_VIOLATION

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 proble

Re: 1.7.7: "STATUS_ACCESS_VIOLATION" bug

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

1.7.7: "STATUS_ACCESS_VIOLATION" bug

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_sta

Re: STATUS_ACCESS_VIOLATION in strlen running a vanilla uw-imapd

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" wrote: > On Wed, Jun 02, 2010 at 03:46:11PM +0200, c...@tocaido

Re: STATUS_ACCESS_VIOLATION in strlen running a vanilla uw-imapd

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 Se

Re: STATUS_ACCESS_VIOLATION in strlen running a vanilla uw-imapd

ve/c/WINDOWS/system32/RPCRT4.dll >(0x77e7) >Secur32.dll => /cygdrive/c/WINDOWS/system32/Secur32.dll >(0x77fe) > >(I am not using the SSL option) > >Here is the stackdump: > >Exception: STATUS_ACCESS_VIOLATION at eip=611097F3 >eax=4D61

STATUS_ACCESS_VIOLATION in strlen running a vanilla uw-imapd

(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, pid 1560, thread main cs=001B ds=00

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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:

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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 ?wrot

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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:18A

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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 >>>  wrote: >>    ^ >>

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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 >> wrote: >^ >. Feeding spammers just makes >them hung

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

On 4/19/2010 7:44 AM, Yuval Emek wrote: On Mon, Apr 19, 2010 at 09:32, Christopher Faylor wrote: ^ . Feeding spammers just makes them hungry. p.envptr is supposed to be filled in by the call to _cygwin_crt0_comm

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

On Mon, Apr 19, 2010 at 09:32, Christopher Faylor 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

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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=

Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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.e

1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions

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

re: Cygwin Vista svn problem STATUS_ACCESS_VIOLATION

I switched so that I needed to access the (same) repository using https:..., the crash started: C:\scratch>svn co https://[host]/[repository] 9 [main] svn 3460 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 1342 [main] svn 3460 open_stackdumpfile: Dumping s

Re: SOLVED: cygwin programs hang or return STATUS_ACCESS_VIOLATION in Windows Vista/2008/7

On Jan 14 14:13, Seth Wegner wrote: > No action or response requested, this is for the next hapless googler. > > If Windows DEP is set to "Turn on DEP for all programs and services > except those I select" certain cygwin-dependent exe files (in my > case, ssh.exe) will hang or return errors. The

SOLVED: cygwin programs hang or return STATUS_ACCESS_VIOLATION in Windows Vista/2008/7

No action or response requested, this is for the next hapless googler. If Windows DEP is set to "Turn on DEP for all programs and services except those I select" certain cygwin-dependent exe files (in my case, ssh.exe) will hang or return errors. The solution is to either select those program

Re: Cygwin Vista svn problem STATUS_ACCESS_VIOLATION

prompt when working with visual studio, so that runtime dependencies are set up properly). C:\svn>\Cygwin\bin\svn checkout https://subversion/trunk/MYDIR tmp 3 [main] svn 3324 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 863 [main] svn 3324 open_stackdumpfile: Dump

Cygwin Vista svn problem STATUS_ACCESS_VIOLATION

runtime dependencies are set up properly). C:\svn>\Cygwin\bin\svn checkout https://subversion/trunk/MYDIR tmp 3 [main] svn 3324 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 863 [main] svn 3324 open_stackdumpfile: Dumping stack trace to svn.exe.stackdump I'

Re: genisoimage with cygwin 1.7 generate STATUS_ACCESS_VIOLATION

exceptions: Exception: > STATUS_ACCESS_VIOLATION > 4487 [main] genisoimage 3948 open_stackdumpfile: Dumping stack trace to > genisoimage.exe.stackdump > >genisoimage.exe.stackdump: >Exception: STATUS_ACCESS_VIOLATION at eip=C128 >eax= ebx= ecx=00229890 edx=7C90E4F4 e

genisoimage with cygwin 1.7 generate STATUS_ACCESS_VIOLATION

Hi, genisoimage 1.1.7.1 (CYGWIN) with cygwin1.dll v1007.0.0.0, 2009-09-11 01:25 throw following error whilte creating a large 2 GB iso file: 694 [main] genisoimage 3948 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 4487 [main] genisoimage 3948 open_stackdumpfile: Dumping

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

On Sun, Jul 05, 2009 at 10:04:42PM -0700, Ian Kelling wrote: >Christopher Faylor wrote: >>It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION >>which is known to occur on Windows 7 with your not-so-serious "Bash >>initialization w/cygwin-1.7". > &g

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Christopher Faylor wrote: It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which is known to occur on Windows 7 with your not-so-serious "Bash initialization w/cygwin-1.7". not-so-serious? Cygwin 1.7 install is very broken because of this bug. Seems serious to me.

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Jerry DeLisle wrote: I am very happy to accept that this problem is something else. Vincent sent a note that it is working for him. I am not sure what "working" means. I have a bash prompt, but none of the default environment variables such as prompts and paths and setting up the home direct

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

On Sun, July 5, 2009 13:49, Jerry DeLisle wrote: > Fresh install still broken with backing down one rev on bash and using > libreadline6. I ran into this Friday as others have noted. The thing that caught me was that the postinstall scripts in the installer rely on a working bash. Once I had a bro

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

still in the wrong thread. Look at the subject. Does it have anything to do with the problem you are having? Apparently it doesn't. It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which is known to occur on Windows 7 with your not-so-serious "Bash initialization w/cygwin

re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Here is some more information: bash-3.2$ ./cygcheck -s >jerrycheck 741 [main] id 85 _cygtls::handle_exceptions: Exception: STATUS_STACK_OVERFLO W 3209 [main] id 85 open_stackdumpfile: Dumping stack trace to id.exe.stackdump garbled output from 'id' command - no uid= found 1206 [main]

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Dave Korn wrote: Vincent R. wrote: bash 3.2.49-22 OK libreadline6 5.2.14-12 OK libreadline7 6.0.3-1OK Jerry DeLisle wrote: bash 3.2.49-22 libreadline6 5.2.14-12 libreadline7 6.0.3-1

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jerry DeLisle on 7/5/2009 1:35 PM: Warning: There are multiple cygwin1.dlls on your path That's probably your culprit. I saw that too and did a full search of the disk and there is only one cygwin1.dll I am also

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jerry DeLisle on 7/5/2009 1:35 PM: > Warning: There are multiple cygwin1.dlls on your path > That's probably your culprit. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -BEGIN PGP SIG

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Vincent R. wrote: > bash 3.2.49-22 OK > libreadline6 5.2.14-12 OK > libreadline7 6.0.3-1OK Jerry DeLisle wrote: > bash 3.2.49-22 > libreadline6 5.2.14-12 > libreadline7 6.0.3-1 Err, ok.

re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

See attached file. Regards, Jerry Cygwin Configuration Diagnostics Current System Time: Sun Jul 05 12:28:58 2009 Windows NT 4 Workstation Ver 4.0 Build 1381 Service Pack 6 Path: C:\WINNT\system32 C:\WINNT D:\cygwin-1.7\bin SysDir: C:\WINNT\System32 WinDir: C:\WINNT PWD = '

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

On Sun, Jul 05, 2009 at 10:49:10AM -0700, Jerry DeLisle wrote: >Moving to this thread: >Vincent R. wrote: >>>I backed down on bash version which required install of libreadline6. >>> >>>bash still fails. This is on NT4. >>> >>>Maybe I need a different combination of binutils, libreadline, and >>>b

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

> Post cygcheck output, both of you, and let's compare. $ cygcheck -c Cygwin Package Information Package VersionStatus _update-info-dir 00826-1OK alternatives 1.3.30c-10 OK ash 20040127-4 OK auto

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Jerry DeLisle wrote: > Moving to this thread: > Vincent R. wrote: >>> I backed down on bash version which required install of libreadline6. >>> >>> bash still fails. This is on NT4. >>> >>> Maybe I need a different combination of binutils, libreadline, and bash. >> I >>> will play with this for a

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Moving to this thread: Vincent R. wrote: >> I backed down on bash version which required install of libreadline6. >> >> bash still fails. This is on NT4. >> >> Maybe I need a different combination of binutils, libreadline, and bash. > I >> will play with this for a bit. >> >> Jerry > > I have ins

Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION

Update: This looks like the same error as Edward Lam posted on 7/2/2009 in response to a bash update announcement. Attached is my cygcheck output. - Ian Kelling Cygwin Configuration Diagnostics Current System Time: Sat Jul 04 23:26:58 2009 Windows Vista Ultimate Ver 6.0 Build 6001 Service Pac

  1   2   >