X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 	tests=AWL,BAYES_00,SPF_NEUTRAL
X-Spam-Check-By: sourceware.org
Message-ID: <4B377101.5050602@cornell.edu>
Date: Sun, 27 Dec 2009 09:36:49 -0500
From: Ken Brown <kbrown AT cornell DOT edu>
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 AT cygwin DOT com
Subject: Re: run2.exe segfaults when GDI and X11 elements are present
References: <4B262E7E DOT 4090001 AT cornell DOT edu> <4B280C6C DOT 90902 AT cwilson DOT fastmail DOT fm> <4B35E98A DOT 3090500 AT cwilson DOT fastmail DOT fm> <4B3621EE DOT 4090108 AT cornell DOT edu> <4B363968 DOT 1090609 AT cornell DOT edu> <4B364DCA DOT 2030601 AT cwilson DOT fastmail DOT fm> <4B365F6A DOT 1090605 AT cornell DOT edu> <4B366863 DOT 9070803 AT cwilson DOT fastmail DOT fm> <4B36E851 DOT 5060205 AT cwilson DOT fastmail DOT fm> <4B372F4A DOT 2000305 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <4B372F4A.2000305@cwilson.fastmail.fm>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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 12/27/2009 4:56 AM, Charles Wilson wrote:
> Charles Wilson wrote:
>> Still hunting the stack corruption/segv bug. PTC!
>
> I think I found it. Before, I was dynamically loading function pointers
> to XOpenDisplay and XCloseDisplay in the main thread, and passing them
> to the worker thread as user data.  By deferring the calls to
> dlopen/dlsym into the worker thread itself, the segvs go away (I'm not
> sure -- it's hard to debug threads other than main in cygwin -- but I
> *think* the function pointers became invalid in the worker thread
> context, in the previous scenario).
>
> So, give r20 a shot. (mintty is still invisible -- but at least run2
> doesn't appear to segfault).

I'm still getting a segfault with test1.xml from

   http://cygwin.com/ml/cygwin/2009-12/msg00871.html

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