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 17:11:00 -0000	[thread overview]
Message-ID: <4D07A55A.1020701@dronecode.org.uk> (raw)
In-Reply-To: <E1PSXPC-0006VD-Sh@cosmos.phy.tufts.edu>

On 14/12/2010 16:07, Ken Olum wrote:
> Thanks for looking into this.  All I need to do to trigger the problem
> is to run paraview.  However, it seems to depend on the details of the
> Linux installation -- system libraries, I suppose.
> 
> On this system it works:
> 
> Mandriva Linux release 2010.1 (Official) for x86_64
> Linux cosmos.phy.tufts.edu 2.6.33.7-server-2mnb #1 SMP Mon Sep 20 19:01:10 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
> 
> Whereas on this one it crashes:
> 
> Red Hat Enterprise Linux Client release 5.5 (Tikanga)
> Linux node12 2.6.18-194.17.4.el5 #1 SMP Wed Oct 20 13:03:08 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
> 
> These two systems are both running the exact same 3.8.1 x86_64 executable
> that I downloaded.
> 
> I attach my Xwin.0.log showing the crash.

Thanks.

Can you try to obtain a backtrace for the crash using the instructions at [1],
please?

[1] http://x.cygwin.com/devel/backtrace.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/


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