public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Olum <kdo@cosmos.phy.tufts.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Server segmentation fault at address 0x306 using ParaView
Date: Tue, 04 Jan 2011 16:08:00 -0000	[thread overview]
Message-ID: <E1Pa9R5-0006Ds-Fi@cosmos.phy.tufts.edu> (raw)
In-Reply-To: <4D20BF02.7010300@dronecode.org.uk> (message from Jon TURNEY on	Sun, 02 Jan 2011 18:08:02 +0000)

   From: Jon TURNEY <jon.turney@dronecode.org.uk>
   Date: Sun, 02 Jan 2011 18:08:02 +0000

   I've updated them to fix the problem, and uploaded a Xserver snapshot at [1].
   [1] ftp://cygwin.com/pub/cygwinx/XWin.20110102-git-29db9091c6ae4995.exe.bz2

This new snapshot works properly and does not crash.  Thanks very much!

   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

I'll try this.  Should I prefer direct rendering from remote machines
that support that and only use AIGLX when I would have indirect
rendering anyway, or should I explicitly request indirect rendering in
order to use AIGLX in all cases?  Thanks again.

                                        Ken

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


  reply	other threads:[~2011-01-04 16:08 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
2011-01-04 16:08               ` Ken Olum [this message]
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=E1Pa9R5-0006Ds-Fi@cosmos.phy.tufts.edu \
    --to=kdo@cosmos.phy.tufts.edu \
    --cc=cygwin-xfree@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).