1.5.22: Error from anything using the cygwin dll

Mikkel Erup mikkelerup@yahoo.com
Mon Nov 27 14:36:00 GMT 2006


--- Mikkel Erup <mikkelerup@yahoo.com> wrote:

> 
> --- "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
> wrote:
> 
> > Mikkel Erup wrote:
> > > I get a message box with the following error trying to run 
> > > any cygwin program:
> > > 
> > > The instruction at "0x6100365f" referenced memory at
> > > "0x006ada90".
> > > The memory could not be "written".
> > > 
> > > id.exe, bash.exe etc. All of them produce the error.
> > > Somtimes, like 1 out of 50 or less a program will succeed.
> > > For example I just ran uname from a windows command window
> > > and it worked the first time, then failed several times.
> > > Sometimes the cygwin.bat script will start the bash shell
> and
> > not
> > > show the above message box. In that case the first lines
> read
> > > "5 [main] bash 3316 dll_crt0_1: internal error: couldn't
> > > determine location of thread function on stack. Expect
> signal
> > > errors.".
> > > Any commands from the bash shell will still produce the
> error
> > > message box described above, though.
> > > The setup program didn't succeed normally either because
> > ash.exe
> > > and bash.exe crashed showing the message box described
> > earlier.
> > > If I boot into safe mode cygwin works but not if I boot
> into
> > > safe mode with network.
> > > I tried killing all processes not vital to running Windows
> as
> > > well as stopping all services. 
> > > Cygwin programs kept producing the error, though.
> > > Output from cygcheck -s -v -r is attached.
> > 
> > 
> > That's because the installation is not complete.  As you
> > describe it,
> > it's a chicken'n'egg thing.  Perhaps removing '/bin/sh' (if
> it
> > exists)
> > and making it a copy of '/bin/bash' will allow 'setup.exe' to
> > finish?
> 
> Making sh.exe a copy of bash.exe and running the installer to
> reinstall produces the same error for bash.exe, ash.exe,
> sed.exe,
> sh.exe, rm.exe, cmp.exe and a some others (The instruction at
> "0x6100365f" referenced memory at "0x006ada90". The memory
> could
> not be "written"). Will try booting to safe and install from
> the hdd to see if it lets the installer complete.
> I am also wondering why cygwin works if I boot to safe mode
> without network. As I said it doesn't work if I boot to safe
> mode with network.
> 
> 
>  
>
____________________________________________________________________________________
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail beta.
> http://new.mail.yahoo.com
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 

Reinstalling from local hdd in safe mode without network allowed
the installer to complete. The problem persists in normal mode,
though


 
____________________________________________________________________________________
Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list