Package: python-vtk
Version: 5.8.0-5
Followup-For: Bug #346182
Thanks for checking the bug again.
I upgraded to python-vtk 5.8.0-5, but I don't get the same
non-crashing behaviour you reported. Is there more to the VTK version
upgrade which still needs to roll in through the servers?
(mayavi2 itself, for instance, currently complains "WARNING: Imported
VTK version (5.8) does not match the one used to build the TVTK
classes (5.6). This may cause problems. Please rebuild TVTK.")
For me python-vtk still segfaults, as before in vtkVRMLImporter::exitField ():
$ gdb python
GNU gdb (GDB) 7.3-debian
...
This GDB was configured as "x86_64-linux-gnu".
...
Reading symbols from /usr/bin/python...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/python
[Thread debugging using libthread_db enabled]
Python 2.7.2+ (default, Nov 30 2011, 19:22:03)
[GCC 4.6.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import vtk
>>> print vtk.vtkVersion.GetVTKVersion()
5.8.0
>>> reader = vtk.vtkVRMLImporter()
>>> reader.SetFileName('mayavi-crash.wrl')
>>> reader.Update()
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe0653cbb in vtkVRMLImporter::exitField() ()
from /usr/lib/libvtkHybrid.so.5.8
(gdb) bt
#0 0x00007fffe0653cbb in vtkVRMLImporter::exitField() ()
from /usr/lib/libvtkHybrid.so.5.8
#1 0x00007fffe0655433 in ?? () from /usr/lib/libvtkHybrid.so.5.8
#2 0x00007fffe0655935 in vtkVRMLImporter::ImportBegin() ()
from /usr/lib/libvtkHybrid.so.5.8
#3 0x00007fffe6bf5f05 in vtkImporter::Read() ()
from /usr/lib/libvtkRendering.so.5.8
#4 0x00007fffe724731d in ?? () from /usr/lib/libvtkRenderingPythonD.so.5.8
#5 0x00000000004b9589 in PyEval_EvalFrameEx ()
#6 0x00000000004bfccd in PyEval_EvalCodeEx ()
#7 0x00000000004c07a2 in PyEval_EvalCode ()
#8 0x00000000004dfa02 in ?? ()
#9 0x00000000004e1415 in PyRun_InteractiveOneFlags ()
#10 0x00000000004e15c8 in PyRun_InteractiveLoopFlags ()
#11 0x00000000004e186f in PyRun_AnyFileExFlags ()
#12 0x00000000004f10ed in Py_Main ()
#13 0x00007ffff69a3ead in __libc_start_main ()
from /lib/x86_64-linux-gnu/libc.so.6
#14 0x000000000041f269 in _start ()
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-vtk depends on:
ii libavcodec53 4:0.7.2-1+b1
ii libavformat53 4:0.7.2-1+b1
ii libavutil51 4:0.7.2-1+b1
ii libc6 2.13-21
ii libgcc1 1:4.6.2-5
ii libmysqlclient16 5.1.58-1
ii libopenmpi1.3 1.4.3-2.1
ii libpq5 9.1.2-1
ii libpython2.7 2.7.2-8
ii libstdc++6 4.6.2-5
ii libswscale2 4:0.7.2-1+b1
ii libvtk5.8 5.8.0-5
ii libx11-6 2:1.4.4-4
ii python 2.7.2-9
ii python-support 1.0.14
ii tcl-vtk 5.8.0-5
ii tcl8.5 8.5.10-1
ii tk8.5 8.5.10-1
ii zlib1g 1:1.2.3.4.dfsg-3
python-vtk recommends no packages.
Versions of packages python-vtk suggests:
pn mayavi2 4.0.0-2
pn vtk-doc <none>
pn vtk-examples <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
