Message-ID: <4B377101.5050602@cornell.edu>
Date: Sun, 27 Dec 2009 09:36:49 -0500
From: Ken Brown <kbrown@cornell.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@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>
In-Reply-To: <4B372F4A.2000305@cwilson.fastmail.fm>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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