X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
Message-ID:	<50B4B89A.5000909@cs.utoronto.ca>
Date:	Tue, 27 Nov 2012 07:56:58 -0500
From:	Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Was: Re: cygwin dlls address issue (cygconv-2.dll), unable to rebaseall
References:	<CADEZfNj7pq1udfPX_9A4Ef6SCJOaX2Lc2xRhWBNGKY1qmVMiAQ AT mail DOT gmail DOT com> <50B3A263 DOT 5020109 AT cs DOT utoronto DOT ca> <CADEZfNg-jDeqRhP43EANm95oXbPV=LdZx7iz9+4OiVH+qZNdbQ AT mail DOT gmail DOT com> <50B3CD06 DOT 1040605 AT cs DOT utoronto DOT ca> <CAG0O4LvsqiXXLNwS9c70RHams0263psigkA6G3ojLHBYWmh0DA AT mail DOT gmail DOT com> <50B3D7C1 DOT 3040607 AT cs DOT utoronto DOT ca> <CADEZfNh0_q5oXU_X1v_pBopyKqYzibn-sAv9mHc2t8Taz6v6ZA AT mail DOT gmail DOT com> <CAG0O4LubadqUsX5=-Xod7umTSn0+FHqdFZcj89tspOL_qJXO=A AT mail DOT gmail DOT com> <50B48938 DOT 2060107 AT gmail DOT com> <CAG0O4Lsno2Exay9K34UD8reFgObRwix9+m2ddwoyTT9MaXQG5Q AT mail DOT gmail DOT com>
In-Reply-To:	<CAG0O4Lsno2Exay9K34UD8reFgObRwix9+m2ddwoyTT9MaXQG5Q@mail.gmail.com>
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 27/11/2012 4:43 AM, Massi wrote:
> 2012/11/27 marco atzeri <marco DOT atzeri AT gmail DOT com>:
>
>> As you have a problem building gdal, you should start a new thread,
>> not reusing the previous one.
> well OK, I believe this is related to the fork problem, not the particular task
> one is performing.
fork() problems in cygwin are like cancer or cerebral palsy... a 
catch-all name for a class of symptoms that can arise from several 
different underlying causes.

Uri's problem was a bad rebase that put his dlls in no-man's land; your 
problem is due to something (thanks, Windows) landing where Cygwin's 
stack wants to be. Unfortunately, I've never seen that particular error, 
and it doesn't print out the addresses involved, so I can't help you as 
easily as I could Uri...

I'd suggest starting that new thread Marco asked for, and attaching to 
it the output of /proc/self/maps for the offending parent process. It 
might give some clues as a starting point.

Ryan


--
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

- Raw text -