public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: kdo@cosmos.phy.tufts.edu Subject: Re: Server segmentation fault at address 0x306 using ParaView Date: Sun, 02 Jan 2011 18:11:00 -0000 [thread overview] Message-ID: <4D20BF02.7010300@dronecode.org.uk> (raw) In-Reply-To: <E1PStzW-0007dR-I8@cosmos.phy.tufts.edu> On 15/12/2010 16:14, Ken Olum wrote: > On the Mandriva 2010.1 host, /usr/lib64/libGL.so.1 is from > lib64mesagl1-7.8.1-6mdv2010.1. On the RHEL host, it is from > mesa-libGL-6.5.1-7.8.el5. Thanks. I was able to reproduce your problem using Centos 5.5 (no RHEL for me :-)) > I have not tried other OpenGL programs, but I can run glxinfo without > a crash on either machine. I attach the results. They are not the > same. In particular, I was surprised to find that RHEL reports > "direct rendering: No" while Mandriva reports "direct rendering: Yes", > although I don't know if this matters when one is running over the > network anyway. Yes, this is the significant difference: The more recent libGL is able to provide direct rendering using the xlib driver, where the software OpenGL renderer is used at the client to render to a pixmap, which is then transferred using xlib to the server. Unfortunately, some rather fragile linkage tricks are used at the moment to make indirect rendering function dispatch work, and it seems they have been broken when we updated to mesa 7.8. I've updated them to fix the problem, and uploaded a Xserver snapshot at [1]. Please give that a try and see if it fixes your problem, if you can. I would suggest that for an application like ParaView, you will probably get much better performance if you use the experimental hardware accelerated OpenGL -wgl mode, see [2] for details. [1] ftp://cygwin.com/pub/cygwinx/XWin.20110102-git-29db9091c6ae4995.exe.bz2 [2] http://cygwin.com/ml/cygwin-xfree-announce/2010-11/msg00000.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2011-01-02 18:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-29 0:27 Ken Olum 2010-12-14 14:54 ` Jon TURNEY 2010-12-14 16:07 ` Ken Olum 2010-12-14 17:11 ` Jon TURNEY 2010-12-14 17:52 ` Ken Olum 2010-12-15 15:00 ` Jon TURNEY 2010-12-15 16:14 ` Ken Olum 2011-01-02 18:11 ` Jon TURNEY [this message] 2011-01-04 16:08 ` Ken Olum 2011-01-05 16:59 ` 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=4D20BF02.7010300@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=kdo@cosmos.phy.tufts.edu \ /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: linkBe 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).