> 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
12 matches
Mail list logo
