From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] mesa 11.0.9-2
Date: Tue, 12 Apr 2016 15:20:00 -0000 [thread overview]
Message-ID: <570D122B.50307@gmail.com> (raw)
In-Reply-To: <announce.201602220900.u1M90xBM023169@int-mx11.intmail.prod.int.phx2.redhat.com>
On 22/02/2016 10:00, Yaakov Selkowitz wrote:
> The following packages have been uploaded to the Cygwin distribution:
>
> * mesa-11.0.9-2
> * dri-drivers-11.0.9-2
> * libglapi0-11.0.9-2
> * libGL1-11.0.9-2
> * libGL-devel-11.0.9-2
> * libOSMesa8-11.0.9-2
> * libOSMesa-devel-11.0.9-2
> * libEGL1-11.0.9-2
> * libEGL-devel-11.0.9-2
> * libGLESv2_2-11.0.9-2
> * libGLESv2-devel-11.0.9-2
> * windowsdriproto-11.0.9-2
>
> Mesa is an open-source implementation of the OpenGL specification, a system
> for rendering interactive 3D graphics.
>
> Complete documentation on OpenGL usage and configuration can be found here:
>
> http://x.cygwin.com/docs/ug/using-glx.html
>
> This release has been rebuilt for LLVM 3.7.
>
> --
> Yaakov
>
Hi Yaakov,
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)
as dri-drivers seems absent from mesa-debuginfo
I can not provide you a meaningful backtrace:
#0 0xfc6d00a0 in ?? ()
#1 0x43934357 in gallium_dri!__driDriverGetExtensions_swrast ()
from E:/cygwin/lib/dri/swrast_dri.so
#2 0x439346c6 in gallium_dri!__driDriverGetExtensions_swrast ()
from E:/cygwin/lib/dri/swrast_dri.so
...
#12 0x43563ce9 in gallium_dri!__driDriverGetExtensions_swrast ()
from E:/cygwin/lib/dri/swrast_dri.so
#13 0x4abfa82c in opengl_renderer::set_polygon_offset (this=0x80610180,
on=false, offset=0)
at /usr/src/debug/octave-4.0.1-1/libinterp/corefcn/gl-render.cc:2916
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)
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
next prev parent reply other threads:[~2016-04-12 15:20 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 [this message]
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 ` [ANNOUNCEMENT] mesa 11.0.9-2 Yaakov Selkowitz
2016-05-25 13:56 ` 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=570D122B.50307@gmail.com \
--to=marco.atzeri@gmail.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).