X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<5c8adab70809261022m71ac4872mc1c9932cd23f5dd@mail.gmail.com>
Date:	Fri, 26 Sep 2008 13:22:47 -0400
From:	"Sean Daley" <spdaley AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Question about cygwin-1.5.25-11 release notes
In-Reply-To:	<48DD0EDA.5020200@users.sourceforge.net>
MIME-Version:	1.0
References:	<5c8adab70809251754j6b96121cq51c145e9cb88f9bf AT mail DOT gmail DOT com> <48DD0EDA DOT 5020200 AT users DOT sourceforge DOT net>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Fri, Sep 26, 2008 at 12:33 PM, Matthew Woehlke <> wrote:
> Sean Daley wrote:
>>
>> I've got a quick question regarding one of the bullet points on the
>> release of cygwin-1.5.25-11.
>>
>> - Fix a crash when creating stackdumps on Windows XP x64 Edition and
>>  Windows 2003 Server x64 Edition.
>>
>> When it says crash, does that mean that the 2003x64 OS actually
>> crashes or a cygwin app will crash
>> on 2003x64?
>
> (Hopefully someone will chime in with a more authoritative answer, but...)
>
> Cygwin runs fine for me on 2k3 x64, so if you're worried that it just
> crashes in general, it doesn't.
>
> I'm guessing that means things that are supposed to non-destructively create
> stack traces (e.g. gdb) would crash, or possibly that the trace you get when
> something crashes for some other reason would cause a second crash (such
> that you don't get the trace).
>
> As we were discussing earlier, userspace apps should not be able to take out
> the OS :-), and since I'm not aware of anything in Cygwin that tries to run
> in kernel space, any OS crashes would not be Cygwin's fault.

I've been following that thread as well too and was pretty sure that
it was not going
to be causing a hardware crash.  I was just informed though that there was some
misinformation given to us and the actual OS was not crashing just the
application
,in general, was crashing.  So we're trying the latest 1.5 dll and
seeing how that goes.

Thanks.

Sean

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

- Raw text -