headers
Jon TURNEY | 2 Jan 2011 19:08
Picon
Favicon
Gravatar

Re: Server segmentation fault at address 0x306 using ParaView

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
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jon TURNEY | 3 Jan 2011 17:55
Picon
Favicon
Gravatar

Re: X server segfault problem

On 02/01/2011 01:11, chm wrote:
> I'm having a problem with cygwin 1.7.7
> and X version 1.9.3.0 where an OpenGL
> application from perl using the Mesa3D
> binding dies in the test with a segfault:

X related questions belong on the cygwin-xfree list.

>   A fatal error has occurred and Cygwin/X
>   will now exit.
> 
>   Caught signal 11 (Segmentation fault).
>   Server aborting.
> 
>   Please open /var/log/xwin/XWin.0.log
>   for more information.
> 
> When I close the popup alert, X exits.
> The XWin.0.log only has Segmentation
> fault at address 0xe.
> 
> I've been unable to determine if the
> problem is in the perl OpenGL module
> code or in the updated X+GLX+Mesa3D.

Even incorrectly written X clients shouldn't make the X server crash, so if
the X server crashes, it is an X server problem.

> To reproduce, just download the perl
> OpenGL module source:
(Continue reading)

Permalink | Reply | 7 comments |
headers
chm | 3 Jan 2011 18:54
Picon

Re: X server segfault problem

On 1/3/2011 11:55 AM, Jon TURNEY wrote:
> On 02/01/2011 01:11, chm wrote:
>> I'm having a problem with cygwin 1.7.7
>> and X version 1.9.3.0 where an OpenGL
>> application from perl using the Mesa3D
>> binding dies in the test with a segfault:
>
> X related questions belong on the cygwin-xfree list.
>
>>    A fatal error has occurred and Cygwin/X
>>    will now exit.
>>
>>    Caught signal 11 (Segmentation fault).
>>    Server aborting.
>>
>>    Please open /var/log/xwin/XWin.0.log
>>    for more information.
>>
>> When I close the popup alert, X exits.
>> The XWin.0.log only has Segmentation
>> fault at address 0xe.
>>
>> I've been unable to determine if the
>> problem is in the perl OpenGL module
>> code or in the updated X+GLX+Mesa3D.
>
> Even incorrectly written X clients shouldn't make the X server crash, so if
> the X server crashes, it is an X server problem.
>
>> To reproduce, just download the perl
(Continue reading)

Permalink | Reply | 6 comments |
headers
chm | 3 Jan 2011 20:32
Picon

Re: X server segfault problem

On 1/3/2011 12:54 PM, chm wrote:
> On 1/3/2011 11:55 AM, Jon TURNEY wrote:
>> On 02/01/2011 01:11, chm wrote:
>>> I'm having a problem with cygwin 1.7.7
>>> and X version 1.9.3.0 where an OpenGL
>>> application from perl using the Mesa3D
>>> binding dies in the test with a segfault:
>>
>> X related questions belong on the cygwin-xfree list.
>>
>>> A fatal error has occurred and Cygwin/X
>>> will now exit.
>>>
>>> Caught signal 11 (Segmentation fault).
>>> Server aborting.
>>>
>>> Please open /var/log/xwin/XWin.0.log
>>> for more information.
>>>
>>> When I close the popup alert, X exits.
>>> The XWin.0.log only has Segmentation
>>> fault at address 0xe.
>>>
>>> I've been unable to determine if the
>>> problem is in the perl OpenGL module
>>> code or in the updated X+GLX+Mesa3D.
>>
>> Even incorrectly written X clients shouldn't make the X server crash, so if
>> the X server crashes, it is an X server problem.
>>
(Continue reading)

Permalink | Reply | 5 comments |
headers
chm | 3 Jan 2011 20:41
Picon

Re: X server segfault problem

On 1/3/2011 2:32 PM, chm wrote:
> On 1/3/2011 12:54 PM, chm wrote:
>> On 1/3/2011 11:55 AM, Jon TURNEY wrote:
>>> On 02/01/2011 01:11, chm wrote:
>>>> I'm having a problem with cygwin 1.7.7
>>>> and X version 1.9.3.0 where an OpenGL
>>>> application from perl using the Mesa3D
>>>> binding dies in the test with a segfault:
>>>
>>> X related questions belong on the cygwin-xfree list.
>>>
>>>> A fatal error has occurred and Cygwin/X
>>>> will now exit.
>>>>
>>>> Caught signal 11 (Segmentation fault).
>>>> Server aborting.
>>>>
>>>> Please open /var/log/xwin/XWin.0.log
>>>> for more information.
>>>>
>>>> When I close the popup alert, X exits.
>>>> The XWin.0.log only has Segmentation
>>>> fault at address 0xe.
>>>>
>>>> I've been unable to determine if the
>>>> problem is in the perl OpenGL module
>>>> code or in the updated X+GLX+Mesa3D.
>>>
>>> Even incorrectly written X clients shouldn't make the X server crash, so if
>>> the X server crashes, it is an X server problem.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Christopher Faylor | 3 Jan 2011 21:08
Favicon

Re: X server segfault problem

On Mon, Jan 03, 2011 at 02:32:15PM -0500, chm wrote:
>I've just added myself to the cygwin-xfree list so this
>reply should go through now.

You don't have to subscribe to the list to send email.  Witness:

http://cygwin.com/ml/cygwin-xfree/2011-01/msg00003.html

--
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/
Permalink | Reply | 0 comments |
headers
Ken Olum | 4 Jan 2011 17:08
Picon
Favicon

Re: Server segmentation fault at address 0x306 using ParaView

   From: Jon TURNEY <jon.turney <at> 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/
Permalink | Reply | 1 comment |
headers
chm | 5 Jan 2011 02:32
Picon

Re: X server segfault problem

On 1/3/2011 2:41 PM, chm wrote:
> On 1/3/2011 2:32 PM, chm wrote:
>> On 1/3/2011 12:54 PM, chm wrote:
>>> On 1/3/2011 11:55 AM, Jon TURNEY wrote:
>>>> On 02/01/2011 01:11, chm wrote:
>>>>> I'm having a problem with cygwin 1.7.7
>>>>> and X version 1.9.3.0 where an OpenGL
>>>>> application from perl using the Mesa3D
>>>>> binding dies in the test with a segfault:
>>>>
>>>> X related questions belong on the cygwin-xfree list.
>>>>
>>>>> A fatal error has occurred and Cygwin/X
>>>>> will now exit.
>>>>>
>>>>> Caught signal 11 (Segmentation fault).
>>>>> Server aborting.
>>>>>
>>>>> Please open /var/log/xwin/XWin.0.log
>>>>> for more information.
>>>>>
>>>>> When I close the popup alert, X exits.
>>>>> The XWin.0.log only has Segmentation
>>>>> fault at address 0xe.
>>>>>
>>>>> I've been unable to determine if the
>>>>> problem is in the perl OpenGL module
>>>>> code or in the updated X+GLX+Mesa3D.
>>>>
>>>> Even incorrectly written X clients shouldn't make the X server crash, so if
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jon TURNEY | 5 Jan 2011 18:00
Picon
Favicon
Gravatar

Re: Server segmentation fault at address 0x306 using ParaView

On 04/01/2011 16:08, Ken Olum wrote:
>    From: Jon TURNEY <jon.turney <at> 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!

Thanks for testing. I'll make an updated package with this change when I 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
> 
> 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.

There's a trade-off here between rendering performance (software rending vs.
hardware acceleration) and network latency (just sending the image vs. sending
lots of OpenGL commands (some of which might be synchronous, requiring a
round-trip for the response))

So, the short answer is, you should try both and see which performs best :-)

Provided your server isn't on the moon, I would guess that ParaView would
behave better with indirect but accelerated rendering, but that's just
speculation.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jon TURNEY | 5 Jan 2011 18:02
Picon
Favicon
Gravatar

Re: X server segfault problem

On 05/01/2011 01:32, chm wrote:
> Final update: I tried on another cygwin install and it worked
> out of the box with the new XWin.2011 program.  Then I went
> back and tried the original system and it now works as
> expected.  Maybe there was a lingering font connection to
> the previous XWin.exe.
> 
> Thanks for the fix,

Thanks for testing. I'll make an updated package with this change when I can.

I can't offer any insight into your 'font errors' since you didn't provide any
details.

--

-- 
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/
Permalink | Reply | 1 comment |

Gmane