DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=PG0hMDEVTlRIa5fd
	Ru8rMzt+QHkJqqtpDDtgyR5IGh3O/ns8MJ4OVuyXvHRucXxG/71oyzCRWit+xRLX
	/fPqV6ddYrv2+to6l2GBdtFQVJoKNYWewEjMAEa0hI/vp5TQR1VeQb0YfwTKMDOp
	sRgiUtmX/hJG+nHmfohUJjvIf5A=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] mesa 11.0.9-2
To: cygwin@cygwin.com
References: <announce.201602220900.u1M90xBM023169@int-mx11.intmail.prod.int.phx2.redhat.com> <570D122B.50307@gmail.com> <570DAFFA.7020700@cygwin.com>
From: Marco Atzeri <marco.atzeri@gmail.com>
Message-ID: <9db412c8-4a84-72e4-cec8-978d8b8bccd5@gmail.com>
Date: Wed, 25 May 2016 11:37:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <570DAFFA.7020700@cygwin.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 13/04/2016 04:33, Yaakov Selkowitz wrote:
> On 2016-04-12 10:20, Marco Atzeri wrote:
>> we found a case where the 32bit is segfaulting
>> while dri-drivers-11.0.9-1
>> works fine.
>> For reference:
>> https://cygwin.com/ml/cygwin/2016-04/msg00245.html
>> https://cygwin.com/ml/cygwin/2016-04/msg00251.html
>>
>> To replicate with octave is enough :
>> run from xterm
>>    /usr/bin/octave-cli-4.0.1.exe
>>
>>   x=1:100;
>>   plot(x,x)
>>
>> However I see that also mesa-demos segfault
>>
>> $ cd /usr/lib/mesa-demos
>> $ ./quad-clip.exe
>> GL_RENDERER   = Gallium 0.4 on llvmpipe (LLVM 3.7, 256 bits)
>> GL_VERSION    = 3.0 Mesa 11.0.9
>> GL_VENDOR     = VMware, Inc.
>> Segmentation fault (core dumped)
>
> I can reproduce this on 32-bit but not 64-bit, and the same happens with
> 11.1.2.  It may be an issue with LLVM 3.7 (11.0.9-1 was built with 3.5)
> but without a useful backtrace it will be hard to pin down.
>

Hi Yaakov,

until the root cause is not pinned down,
can you re-put 11.0.9-1 as current for 32bit and
leave all the new version as tests ?

With current 11.2.2-1 and previous 11.2.1-1 both not working
we have an issue.

Regards
Marco


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