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: Tue, 14 Dec 2010 14:54:00 -0000	[thread overview]
Message-ID: <4D078510.9000903@dronecode.org.uk> (raw)
In-Reply-To: <E1PMra5-0005aX-QF@cosmos.phy.tufts.edu>

On 29/11/2010 00:26, Ken Olum wrote:
> Running paraview 3.8.1 (see http://paraview.org) on a Linux client
> (Mandriva 2010.0 or Red Hat Enterprise Server 5.5) causes a crash of
> my Cygwin/X (release 1.9.2.0) with "Segmentation fault at address
> 0x306".  Any ideas?

Thanks for the problem report.

In a quick test, I wasn't able to reproduce this crash using paraview 3.8.1 on
Fedora 14. Do you need to do anything other than just start paraview to
demonstrate the problem?

> Paraview uses OpenGL.  Perhaps that is related.


> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html

Can you attach your /var/log/xwin/XWin.0.log, please.

> Documentation:         http://x.cygwin.com/docs/
> FAQ:                   http://x.cygwin.com/docs/faq/

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


  reply	other threads:[~2010-12-14 14:54 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 [this message]
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
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=4D078510.9000903@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: 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).