Bug#346182: Bug#822321: crashes when importing VRML file (containing PROTO)

Drew Parsons dparsons at debian.org
Sat May 7 12:45:13 UTC 2016


reopen 346182 
reassign 346182 libvtk6.2
thanks

This bug is still present for the same test file. 
A gdb backtrace pins it on vtkVRMLImporter::exitField()
from /usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2, 
which is in package libvtk6.2.

It's essentially the same backtrace as before, only coming through 
libvtkIOImport-6.2.so.6.2 instead of libvtkHybrid.so.5.8

Here is the backtrace for the python execution:

$ gdb python
GNU gdb (Debian 7.10-1+b1) 7.10
...
Reading symbols from python...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/python 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 2.7.11+ (default, Apr 17 2016, 14:00:29) 
[GCC 5.3.1 20160409] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import vtk
[New Thread 0x7fffadefa700 (LWP 27119)]
...
>>> reader = vtk.vtkVRMLImporter()
>>> reader.SetFileName('mayavi-crash.wrl')
>>> reader.Update()

Program received signal SIGSEGV, Segmentation fault.
0x00007fff9bab3f3b in vtkVRMLImporter::exitField() () from /usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
(gdb) bt
#0  0x00007fff9bab3f3b in vtkVRMLImporter::exitField() () from /usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#1  0x00007fff9baaf864 in ?? () from /usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#2  0x00007fff9bab0ee2 in vtkVRMLImporter::ImportBegin() () from /usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#3  0x00007fff9baabcbd in vtkImporter::Read() () from /usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#4  0x00007fff9bcd2435 in ?? () from /usr/lib/x86_64-linux-gnu/libvtkIOImportPython27D-6.2.so.6.2
#5  0x00000000004c4aca in PyEval_EvalFrameEx ()
#6  0x00000000004c2bd5 in PyEval_EvalCodeEx ()
#7  0x00000000004c2979 in PyEval_EvalCode ()
#8  0x00000000004f221f in ?? ()
#9  0x000000000044c6f0 in PyRun_InteractiveOneFlags ()
#10 0x000000000044c530 in PyRun_InteractiveLoopFlags ()
#11 0x000000000042ea01 in ?? ()
#12 0x000000000049de78 in Py_Main ()
#13 0x00007ffff6f1a610 in __libc_start_main (main=0x49d7a0 <main>, argc=1, argv=0x7fffffffe0b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe0a8) at libc-start.c:291
#14 0x000000000049d6c9 in _start ()



More information about the debian-science-maintainers mailing list