[Paraview] segmentation fault

[Scott, W Alan]

Also known as "when all else fails, rebuild from scratch..."  :-)

Alan 

-----Original Message-----
From: paraview-bounces at paraview.org [mailto:paraview-bounces at paraview.org] On Behalf Of Peter Brady
Sent: Monday, April 20, 2009 5:06 PM
To: Berk Geveci
Cc: ParaView
Subject: Re: [Paraview] segmentation fault

I recompiled with debug and the seg fault went away.  I then recompiled it with the standard build and the seg fault was still gone.  At this point I'm fairly confused as to what caused the original seg fault but I'm willing to chalk it up to the mysterious force that works to extend a grad student's time in school to unreasonable levels.

thanks,
Peter.

On Sat, Apr 18, 2009 at 1:55 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
> Would it be too painful to compile paraview with debug and to get a 
> full stack trace? We may also ask you to attach to paraview with a 
> debugger depending on what the stack looks like.
>
> On Fri, Apr 17, 2009 at 1:34 PM, Peter Brady <petertbrady at gmail.com> wrote:
>> I don't mean to flood the list but after some investigation it 
>> appears that the PNGWriter is the ONLY image writer that leads to a seg fault.
>>  All the others work fine.
>>
>> On Fri, Apr 17, 2009 at 10:05 AM, Peter Brady <petertbrady at gmail.com> wrote:
>>> Dear all,
>>>
>>> I am trying to install paraview such that I can do remote rendering 
>>> through python scripting without the time consuming difficulty of 
>>> having the render window pop up.  I've compiled mesa with osmesa 
>>> support inorder to take advantage of the --use-offscreen-rendering 
>>> option.
>>>
>>> Everything compiled correctly and things start running but when I 
>>> try to write the image I get a segmentation fault.  I started 
>>> paraview under gdb and found the source of the segmentation fault 
>>> when trying to save an image:
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x00002aaab7c31f2a in vtkPNGWriter::WriteSlice ()
>>>   from /opt/paraview-mpi/lib/paraview-3.4/libvtkIO.so.pv3.4
>>> Missing separate debuginfos, use: debuginfo-install
>>> e2fsprogs-libs-1.41.4-4.fc10.x86_64 expat-2.0.1-5.x86_64
>>> keyutils-libs-1.2-3.fc9.x86_64 krb5-libs-1.6.3-18.fc10.x86_64
>>> libXau-1.0.4-1.fc10.x86_64 libXdmcp-1.0.2-6.fc10.x86_64
>>> libXt-1.0.5-1.fc10.x86_64 libgcc-4.3.2-7.x86_64
>>> libselinux-2.0.78-1.fc10.x86_64 libstdc++-4.3.2-7.x86_64
>>> libxcb-1.1.91-5.fc10.x86_64 ncurses-libs-5.6-20.20080927.fc10.x86_64
>>> python-libs-2.5.2-1.fc10.x86_64 qt-x11-4.4.3-15.fc10.x86_64
>>> readline-5.2-13.fc9.x86_64
>>>
>>> I'm using paraview 3.4 and mesa 7.4 on fedora 10.  Any ideas as to 
>>> what's causing this and how to fix it?
>>>
>>> Thanks,
>>> Peter.
>>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at: 
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview