If you could do a debug build and then post the stack trace that would
be. Of great help to identify the problem.
Utkarsh
On Jul 5, 2009, at 8:44 AM, Wim van der Meer <[email protected]>
wrote:
Today I had some time to set up Qt 4.3.5, and I had the same crash.
Since this problem is not reproducible by you, it may be something in
the way I have set up things.
As soon as 3.6 is released I will try the official binaries.
Wim
On Fri, Jul 3, 2009 at 5:41 AM, Berk Geveci<[email protected]>
wrote:
I can't reproduce in 4.5 either.
-berk
On Thu, Jul 2, 2009 at 9:22 AM, Utkarsh
Ayachit<[email protected]> wrote:
Qt 4.5 is not officially supported for 3.6 releases so you may run
into issues (not sure this is one of those). However since I can't
reproduce it, can you try if it's reproducible with Qt 4.3.5?
Utkarsh
On Wed, Jul 1, 2009 at 8:27 PM, Wim van der Meer<[email protected]
> wrote:
It is not a debug build. I am also using a linux 64 bit platform.
Maybe I should mention that I am using Qt 4.5.0
Here is the output when using gdb:
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) run
Starting program: /home/wim/Software/Paraview/paraview-3.6/build/
bin/paraview
Executing new program:
/home/wim/Software/Paraview/paraview-3.6/build/bin/paraview-real
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9a5dd53790 (LWP 6290)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f9a5dd53790 (LWP 6290)]
0x00007f9a5bbf51ec in QWidgetPrivate::clipRect () from /usr/lib/
libQtGui.so.4
(gdb)
Thanks for looking into this.
Wim
On Wed, Jul 1, 2009 at 10:16 PM, Utkarsh
Ayachit<[email protected]> wrote:
Seems to work for me (even when visibility is changed using
display
tab) on linux-64 bit. Is that a debug build? Can you provide the
stack
trace or attach with a debugger and see where it's crashing?
Thanks
Utkarsh
On Tue, Jun 30, 2009 at 9:35 PM, Wim van der
Meer<[email protected]> wrote:
To reproduce the crash:
1. Open a png image file
2. Close the 2D view
3. Create a 3D view
4. In the Object Inspector Display tab click the Visible checkbox
5. Paraview crashes
In step 4, clicking the eye in the pipeline browser doesn't
crash the software.
Wim van der Meer
_______________________________________________
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
--
\/\///\/\
_______________________________________________
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
