Re: Bash: Cannot execute binary file

Buchbinder, Barry (NIH/NIAID) [E] niaid.nih.gov> writes: > > Eliot Moss sent the following at Monday, March 28, 2011 10:28 PM > >Why not just use the Windows version and invoke it from cygwin (if > >cygwin is the environment from which you want to do that)? It is easy > >to invoke Windows progra

dlopen() differences on CYGWIN_NT-5.1 and CYGWIN_NT-6.1

Hello everyone, I have two equal cygwin installations (with respect to installed packages). One on Windows 7 and one on Windows XP. I always used the Windows XP version for "porting" my application (which relies heavily on dlopen) to Windows. However, I finally wanted to make the move to Windows

Re: Best way to repair cygwin?

You can select "re-install" in the package manager. Just toggel the icon next to "All" (at the top) until it reads "re-install". I like to keep a back up of anything I have added or configured, such as the path folders and such. That way, if I have to wipe out the cygwin folder and start again

cygwin/vmware_template/ssh verison issue with 1.126

I have a 2003 template with a working Cygwin sshd install. I deploy vms via script from that template and when they are brought online the Cygwin prompt is now '#' instead of a '$' and I cannot start sshd. Both Cygwin sshd service are configured with the cyg_server account to start them. A

sshd win2003 CYGWIN_NT-5.2 1.7.7(0.230/5/3)

Hello Having an issue with Cygwin and sshd service starting.  This was working at one point and these machines were handed off to QA and now when deploying templates from said machine the Cygwin permissions seemed to be fubar'd.  When running Cygwin with any account we have a # prompt instead o

SOLVED (was: Re: fixing fork failures (was: Re: Best way to repair cygwin?))

> > This is typically the result of one of two things: > > > > 1. > > > > 2. DLL collisions - Install the 'rebase' package, read its README in > > /usr/share/doc/Cygwin, and follow the instructions there to run > > 'rebaseall'. Thanks a lot! In my

Re: fixing fork failures (was: Re: Best way to repair cygwin?)

On 26/08/2011 9:22 AM, Ronald Fischer wrote: 9420794 [main] sh 8004 exception::handle: Exception: STATUS_ACCESS_VIOLATION sh: fork: retry: Resource temporarily unavailable I had run setup again yesterday evening I wonder whether there is an easy way to "repair" Cygwin Quoting Larry's recent res

Best way to repair cygwin?

Cygwin worked well so far. However, starting with today, I get the following error - for example when invoking bash: MUCNL3E6880:~ 2 23 $ bash --norc 163 [main] bash 5788 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1958 [main] bash 5788 open_stackdumpfile: Dumping stack trace

Re: STC for libapr1 failure

On Aug 25 17:39, David Rothenberger wrote: > For a while now, the test cases that come with libapr1 have been > bombing with this message: > > *** fatal error - NtCreateEvent(lock): 0xC035 > > I finally took some time to investigate and have extracted a STC > that demonstrates the problem.