Mail Archives: cygwin/2008/09/26/14:57:32
On Fri, Sep 26, 2008 at 01:22:47PM -0400, Sean Daley wrote:
>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.
The message says that something was fixed four releases and three months
prior to the current shipping version of the Cygwin DLL. I don't see
any reason to be concerned about upgrading to an even newer release.
The announcement said that the problem was FIXED after all.
cgf
--
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 -