X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4B38F620.1050405@cornell.edu> Date: Mon, 28 Dec 2009 13:17:04 -0500 From: Ken Brown User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: run2.exe segfaults when GDI and X11 elements are present References: <4B262E7E.4090001@cornell.edu> <4B280C6C.90902@cwilson.fastmail.fm> <4B35E98A.3090500@cwilson.fastmail.fm> <4B3621EE.4090108@cornell.edu> <4B363968.1090609@cornell.edu> <4B364DCA.2030601@cwilson.fastmail.fm> <4B365F6A.1090605@cornell.edu> <4B366863.9070803@cwilson.fastmail.fm> <4B36E851.5060205@cwilson.fastmail.fm> <4B372F4A.2000305@cwilson.fastmail.fm> <4B377101.5050602@cornell.edu> <4B37C69A.7070003@cwilson.fastmail.fm> <4B37E04D.7080201@cornell.edu> <4B37E2B9.8020801@cornell.edu> <4B386A9E.9030102@cwilson.fastmail.fm> <4B38BA90.7030704@cornell.edu> <4B38CF63.5000409@cwilson.fastmail.fm> <4B38DBEE.2050600@cornell.edu> <4B38E503.9020209@cwilson.fastmail.fm> In-Reply-To: <4B38E503.9020209@cwilson.fastmail.fm> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 12/28/2009 12:04 PM, Charles Wilson wrote: > Ken Brown wrote: >> Sorry for the confusion. I've just tried the xml file above with both >> r24 and r25, and I get a segfault unless DISPLAY is set in the >> environment. I hadn't noticed previously that this was still broken >> because I had fixed my own test.xml file by adding the SelfOption you >> suggested. > > Fixed in r27. Can you confirm? I believe this is the last of the known > errors in your various test cases -- which isn't to say there might be > others. But if you can confirm that all of the already-reported errors > are fixed, then > (a) let's start a new thread with any new errors, > (b) or if this is working for you, then I might go ahead and release > run2-0.4.0 tonight or tomorrow. r27 works fine for me. All previously reported errors are fixed, and I haven't found any new ones. Thanks. Ken -- 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