From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] mesa 11.0.9-2
Date: Wed, 13 Apr 2016 02:33:00 -0000 [thread overview]
Message-ID: <570DAFFA.7020700@cygwin.com> (raw)
In-Reply-To: <570D122B.50307@gmail.com>
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.
--
Yaakov
--
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
next prev parent reply other threads:[~2016-04-13 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 9:08 Yaakov Selkowitz
2016-04-12 15:20 ` Marco Atzeri
2016-04-13 2:17 ` gdb using Windows paths in dlopen()ed modules? Yaakov Selkowitz
2016-04-13 8:09 ` Corinna Vinschen
2016-04-13 2:33 ` Yaakov Selkowitz [this message]
2016-05-25 13:56 ` [ANNOUNCEMENT] mesa 11.0.9-2 Marco Atzeri
[not found] ` <b8ee7d32-504d-27d8-51ab-547ea7a51968@dronecode.org.uk>
2016-06-03 17:56 ` Jon Turney
2016-06-06 7:25 ` Yaakov Selkowitz
2016-06-06 14:27 ` Jon Turney
2016-06-09 22:01 ` [ANNOUNCEMENT] mesa 11.0.9-2 [GOLDSTAR] Yaakov Selkowitz
2016-06-10 4:36 ` Marco Atzeri
2016-06-10 8:31 ` Corinna Vinschen
2016-06-10 14:49 ` Andrew Schulman
2016-06-20 18:29 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570DAFFA.7020700@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).