public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: xorg-server-1.17.1-3
Date: Fri, 01 May 2015 22:39:00 -0000	[thread overview]
Message-ID: <5543E4AC.5010304@dronecode.org.uk> (raw)
In-Reply-To: <5543E14A.1010802@cornell.edu>

On 01/05/2015 21:25, Ken Brown wrote:
> On 5/1/2015 2:19 PM, Jon TURNEY wrote:
>> On 01/05/2015 13:43, Ken Brown wrote:
>>> On 5/1/2015 7:56 AM, Jon TURNEY wrote:
>>>> On 30/04/2015 23:19, Ken Brown wrote:
>>>>> I'm finding, on three different 64-bit Cygwin systems, that the server
>>>>> dies shortly after starting.  I'm attaching XWin.0.log from one of
>>>>> them.
[...]
>>
>> I don't quite understand why cygwin's exception processing doesn't then
>> catch that exception and raise a SIGSEGV.
>>
>> However, I did a bit more staring at the changes in 1.17.1-3 and I did
>> find a nasty bug in some code which uses the heap.  I've uploaded a
>> snapshot [1] with a possible fix, please test that if you can.
>
> That fixes it.  Thanks.

No problem.  Thanks for testing, and thanks for reporting the bug!

I've uploaded 1.17.1-4 with this fix.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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

      reply	other threads:[~2015-05-01 20:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 18:10 Jon TURNEY
2015-04-30 22:19 ` Ken Brown
2015-05-01 11:57   ` Jon TURNEY
2015-05-01 12:43     ` Ken Brown
2015-05-01 18:51       ` Jon TURNEY
2015-05-01 20:38         ` Ken Brown
2015-05-01 22:39           ` Jon TURNEY [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5543E4AC.5010304@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=kbrown@cornell.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).