On 20/03/2016 09:05, Ivan Pozdeev wrote:
gdb
---
I managed to debug the gdb session with VisualGDB (trial).
It turns out, the root cause is that the /bin/sh executable is x64, but
the core file `sh.exe.core' - of the same executable - has i386 format!
(objdump: <...>sh.exe.core: file format e
20.03.2016 15:47, Marco Atzeri пишет:
On 20/03/2016 10:05, Ivan Pozdeev wrote:
bash
I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backtick
On 20/03/2016 10:05, Ivan Pozdeev wrote:
bash
I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backticks. Other times, commands with stream redi
bash
I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backticks. Other times, commands with stream redirection fail
silently or produce nothing
I am able to repro this every time:
1. Launch a Windows Server 2003 x64 image (I used ami-dc4daab5) on a high
compute x-large (c1.xlarge) instance of EC2.
2. Install the default cygwin
3. Open up a bash shell
4. Type 'if [ "1" == "1" ]; then echo hello; fi'
5. Watch bash crash
I looked through
> And maybe instead of trying to pay a thankful compliment to the
maintainers
> of the project, I'll just keep my trap shut for the abuse on an oversight.
And maybe I just need a vacation for having snapped that off in anger so
fast. Sorry for the list-spam, folks.
--
Unsubscribe info: http
> If you really like Cygwin then maybe you'll do us the favor of honoring
> the conventions of the Cygwin mailing list and stop pointlessly adding
> header information in the body of your email. There really is no reason
> for this duplication and it only serves to feed the spammers.
And maybe in
Thursday, October 23, 2008 2:54 PM
>To: [EMAIL PROTECTED]
>Subject: Re: cygwin bash crashes on Win Serv 2008
If you really like Cygwin then maybe you'll do us the favor of honoring
the conventions of the Cygwin mailing list and stop pointlessly adding
header information in the body of y
cygwin@cygwin.com
Subject: Re: cygwin bash crashes on Win Serv 2008
On Oct 23 17:52, Dave Korn wrote:
> Corinna Vinschen wrote on 23 October 2008 17:21:
> > Attempt to execute non-executable address 00419d97
> >
> > Huh? Why should this address (this application funct
FYI, Microsoft Professional Support EMEA didn't accept this problem as a
support case. So, if nobody at Microsoft thinks this is a potential OS
problem and requires analyzing from the OS side, it will stay unfixed.
On Oct 23 20:53, Corinna Vinschen wrote:
> On Oct 23 17:52, Dave Korn wrote:
> > C
On Oct 23 17:52, Dave Korn wrote:
> Corinna Vinschen wrote on 23 October 2008 17:21:
> > Attempt to execute non-executable address 00419d97
> >
> > Huh? Why should this address (this application function) be
> > "non-executable", while it's executable when TS is not installed?
>
> DEP? AS
Freddy Jensen wrote on 23 October 2008 18:00:
> I forgot to mention that for us, it happens on a 64-bit version
> of Win Serv 2008. We have not tried it on a 32-bit version.
I believe that would suggest this is a side-effect of DEP being opt-out by
default on win64 and opt-in by default on win
Corinna Vinschen wrote on 23 October 2008 17:21:
>> Only thing I can think of is "Not if %ss has been mucked around with it
>> isn't".
>
> Yeah, I heard about that. But what is %ss doing in Windows
Same as usual. Pointing to the stack segment. It just /happens/ that the
SS is a full 32-b
On Oct 23 16:40, Dave Korn wrote:
> Corinna Vinschen wrote on 23 October 2008 15:09:
> > I seem to have missed the point here. The point is, this `push %ebp'
> > instruction is the one crashing, producing a segmentation violation.
>
> What's the underlying windows exception (i.e. before cygwin
Corinna Vinschen wrote on 23 October 2008 15:09:
>> The crashes don't occur in Cygwin, but in the application code. As I
>> said, one of the crashing apps is bash. I created a full debug bash
>> version and a special debug version of GDB which, for some reason, runs
>> fine, in contrast to the n
On Oct 23 15:54, Corinna Vinschen wrote:
> On Oct 20 14:42, Freddy Jensen wrote:
> >
> > Apparently the cygwin bash crash on Win Serv 2008 is related to the
> > "Terminal Services" on Windows. It looks like the problem is not
> > there if the Terminal Services has not been installed/started.
>
>
On Oct 20 14:42, Freddy Jensen wrote:
>
> Apparently the cygwin bash crash on Win Serv 2008 is related to the
> "Terminal Services" on Windows. It looks like the problem is not
> there if the Terminal Services has not been installed/started.
I can confirm this observation. It doesn't matter if t
Freddy Jensen wrote:
> Has anyone tried cygwin on a 64-bit Windows Server 2008 system?
Seems it only runs under WoW/cmd, not the regular cmd... another fine
mess from Microsoft.
--
René Berber
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygw
On Sun, Oct 19, 2008 at 08:12:35AM -0700, Freddy Jensen wrote:
>Has anyone tried cygwin on a 64-bit Windows Server 2008 system?
>
>After I install it, bash crashes on startup like this:
>
>Exception: STATUS_ACCESS_VIOLATION at eip=0043AE30
>eax= ebx= ecx=61106EC
Scott Webster Wood wrote:
I saw the following posting after experiencing a similar problem.
One of the follow ups suggested running cygwin.bat and reporting the
result, but the result is the same whether I try to run cygwin.bat,
call bash directly from a cmd.exe shell or call bash from something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to loch-schwarz on 2/1/2007 3:21 PM:
>
> Any ideas what might be going wrong?
>
> I did have an older version of cygwin on my maschine a while back -
> could this be causing problems?
Yes, it could. But to know for sure, post the output o
I hope this is not too vague...
I have tried to install 1.5.24-2 using setup.exe and while the
download appears to work correctly, as soon as the scripts are run, I
get a series of crashes by bash (sorry about the german messages):
Fehlgeschlagene Anwendung ash.exe, Version 0.0.0.0, fehlgeschla
Hi,
I uninstalled Outpost Firewall Pro 4 completely (just disabling
loading it didn't work) and cygwin is live now! Thanks very much.
--
The fish that is singing in Ucayaly river...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/pro
Well, from your cygcheck:
> Path: C:\Program Files\Far
> C:\WINDOWS\system32
> C:\WINDOWS
> C:\WINDOWS\System32\Wbem
> C:\WUsr\atit\ATI Control Panel
> C:\usr\shared\Compuware\NMShared
> C:\usr\shared\Compuware\
> C:\WUsr\Subversion\bin
> C:\SFU\c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#PPIOSPE; redirecting to the list.
According to Serge Skorokhodov on 12/26/2006 3:42 AM:
> Hi,
>
> I've attempted a clean default cygwin install and the error is the same.
>
> Error signature:
> AppName: bash.exe AppVe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Serge Skorokhodov on 12/25/2006 5:48 PM:
> Hi,
>
> I updated cygwin to the lates version on my WinXP SP2 notebook with
> all recent updates and encounter a stopping problem. bash starts to
> crash during setup script execution and cygwin
Hi,
I updated cygwin to the lates version on my WinXP SP2 notebook with
all recent updates and encounter a stopping problem. bash starts to
crash during setup script execution and cygwin does not work any more.
Playing with the versions of cygwin1.dll etc. were no success. Does
anybody encounter
On Mon, Nov 14, 2005 at 02:17:04PM -0400, Rodrigo Medina wrote:
>I have just installed the cygwin1-20051114 snapshot in a W98 box. The
>cygwin.bat crashes. The alert window says that inside BASH there is an
>illegal instruction. After that the machine was blocked and I had to
>restart using the
Hi,
I have just installed the cygwin1-20051114 snapshot in a W98 box.
The cygwin.bat crashes. The alert window says that inside BASH there is
an illegal instruction. After that the machine was blocked and I had to
restart using the hardware reset. The apparently the rxvt.bat works OK.
The previous
29 matches
Mail list logo
