Bug#346182: Bug#822321: crashes when importing VRML file (containing PROTO)
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.
0x7fff9bab3f3b in vtkVRMLImporter::exitField() () from
/usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
(gdb) bt
#0 0x7fff9bab3f3b in vtkVRMLImporter::exitField() () from
/usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#1 0x7fff9baaf864 in ?? () from
/usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#2 0x7fff9bab0ee2 in vtkVRMLImporter::ImportBegin() () from
/usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#3 0x7fff9baabcbd in vtkImporter::Read() () from
/usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2
#4 0x7fff9bcd2435 in ?? () from
/usr/lib/x86_64-linux-gnu/libvtkIOImportPython27D-6.2.so.6.2
#5 0x004c4aca in PyEval_EvalFrameEx ()
#6 0x004c2bd5 in PyEval_EvalCodeEx ()
#7 0x004c2979 in PyEval_EvalCode ()
#8 0x004f221f in ?? ()
#9 0x0044c6f0 in PyRun_InteractiveOneFlags ()
#10 0x0044c530 in PyRun_InteractiveLoopFlags ()
#11 0x0042ea01 in ?? ()
#12 0x0049de78 in Py_Main ()
#13 0x76f1a610 in __libc_start_main (main=0x49d7a0 , argc=1,
argv=0x7fffe0b8, init=, fini=,
rtld_fini=, stack_end=0x7fffe0a8) at libc-start.c:291
#14 0x0049d6c9 in _start ()
Bug#346182:
forwarded 346182 http://vtk.org/Bug/view.php?id=12776
thanks
I can reproduce this issue on my machine too:
Here is the full backtrace with vtk compiled in debug mode:
Program received signal SIGSEGV, Segmentation fault.
0x7701ec32 in vtkPoints::GetPoint (this=0x77f63a98, id=0)
at /home/mathieu/Kitware/VTK/Common/vtkPoints.h:117
117 double *GetPoint(vtkIdType id) { return this-Data-GetTuple(id);};
(gdb) bt
#0 0x7701ec32 in vtkPoints::GetPoint (this=0x77f63a98,
id=0) at /home/mathieu/Kitware/VTK/Common/vtkPoints.h:117
#1 0x7719237d in vtkVRMLImporter::exitField (this=0x639240)
at /home/mathieu/Kitware/VTK/Hybrid/vtkVRMLImporter.cxx:6056
#2 0x7718ba94 in yyparse (self=0x639240) at
/home/mathieu/Kitware/VTK/Hybrid/vtkVRMLImporter.cxx:1358
#3 0x7718e8e3 in vtkVRMLImporter::ImportBegin (this=0x639240)
at /home/mathieu/Kitware/VTK/Hybrid/vtkVRMLImporter.cxx:5413
#4 0x767e2625 in vtkImporter::Read (this=0x639240) at
/home/mathieu/Kitware/VTK/Rendering/vtkImporter.cxx:79
#5 0x00400b6c in vtkImporter::Update (this=0x639240) at
/home/mathieu/Kitware/VTK/Rendering/vtkImporter.h:76
#6 0x00400af7 in main (argc=2, argv=0x7fffe678) at /tmp/v/bla.cxx:8
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#346182:
tags 346182 moreinfo
thanks
At least it does not crash anymore in vtk 5.8.0-5, but properly report
the file is not supported. Since this is not a crash, I would be
tempted to close this bug now.
Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48)
[GCC 4.4.5] on linux2
Type help, copyright, credits or license for more information.
import vtk
reader = vtk.vtkVRMLImporter()
reader.SetFileName('mayavi-crash.wrl')
reader.Update()
ERROR: In /home/mathieu/tmp/vtk-5.8.0/Hybrid/vtkVRMLImporter.cxx, line 5425
vtkVRMLImporter (0xce8720): Unable to open file: mayavi-crash.wrl
print vtk.vtkVersion.GetVTKVersion()
5.8.0
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#346182: crashes when importing VRML file (containing PROTO)
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.
0x7fffe0653cbb in vtkVRMLImporter::exitField() ()
from /usr/lib/libvtkHybrid.so.5.8
(gdb) bt
#0 0x7fffe0653cbb in vtkVRMLImporter::exitField() ()
from /usr/lib/libvtkHybrid.so.5.8
#1 0x7fffe0655433 in ?? () from /usr/lib/libvtkHybrid.so.5.8
#2 0x7fffe0655935 in vtkVRMLImporter::ImportBegin() ()
from /usr/lib/libvtkHybrid.so.5.8
#3 0x7fffe6bf5f05 in vtkImporter::Read() ()
from /usr/lib/libvtkRendering.so.5.8
#4 0x7fffe724731d in ?? () from /usr/lib/libvtkRenderingPythonD.so.5.8
#5 0x004b9589 in PyEval_EvalFrameEx ()
#6 0x004bfccd in PyEval_EvalCodeEx ()
#7 0x004c07a2 in PyEval_EvalCode ()
#8 0x004dfa02 in ?? ()
#9 0x004e1415 in PyRun_InteractiveOneFlags ()
#10 0x004e15c8 in PyRun_InteractiveLoopFlags ()
#11 0x004e186f in PyRun_AnyFileExFlags ()
#12 0x004f10ed in Py_Main ()
#13 0x769a3ead in __libc_start_main ()
from /lib/x86_64-linux-gnu/libc.so.6
#14 0x0041f269 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 libpq59.1.2-1
ii libpython2.7 2.7.2-8
ii libstdc++64.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 python2.7.2-9
ii python-support1.0.14
ii tcl-vtk 5.8.0-5
ii tcl8.58.5.10-1
ii tk8.5 8.5.10-1
ii zlib1g1: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
Bug#346182: Not a bug in Mayavi2
This is a bug in VTK, IMHO. You can reproduce the crash using the
following Python code (using the swig VTK bindings):
import vtk
reader = vtk.vtkVRMLImporter()
reader.SetFileName('foo.wrl')
reader.Read()
Running gdb on this gives the following backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7d506c0 (LWP 20790)]
0xb462dc71 in vtkVRMLImporter::exitField () from
/usr/lib/libvtkHybrid.so.5.0
(gdb) backtrace
#0 0xb462dc71 in vtkVRMLImporter::exitField ()
from /usr/lib/libvtkHybrid.so.5.0
#1 0xb46322f8 in yyparse () from /usr/lib/libvtkHybrid.so.5.0
#2 0xb46326d7 in vtkVRMLImporter::ImportBegin ()
from /usr/lib/libvtkHybrid.so.5.0
#3 0xb5feb8cc in vtkImporter::Read () from
/usr/lib/libvtkRendering.so.5.0
#4 0xb61d607e in ?? () from /usr/lib/libvtkRenderingPythonD.so.5.0
#5 0x080de562 in PyEval_EvalFrameEx ()
#6 0x080e00b8 in PyEval_EvalCodeEx ()
#7 0x080e0217 in PyEval_EvalCode ()
#8 0x080fe0e1 in PyRun_FileExFlags ()
#9 0x080fe43a in PyRun_SimpleFileExFlags ()
#10 0x0805c882 in Py_Main ()
#11 0x0805b972 in main ()
I believe the bug should be reallocated.
Gaël
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#346182: crashes when importing VRML file (containing PROTO)
Package: mayavi Version: 1.4-1 Severity: normal mayavi segfaults when asked to import the attached VRLM file (displaying a single sphere). I presume it crashes because of the PROTO, since mayavi is able to read in an equivalent file drawing a sphere directly without using PROTO. I assume the sample itself file is not faulty since other VRML viewers such as gtklookat or freewrl are able to read it successfully. Thanks, Drew -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.14 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages mayavi depends on: ii libvtk4-dev 4.4.2-8VTK header files for building C++ ii python2.3.5-3An interactive high-level object-o ii python-tk 2.3.5-3Tkinter - Writing Tk applications ii python-vtk4.4.2-8Python bindings for VTK mayavi recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346182: sample file
Here is the sample file which crashes mayavi. mayavi-crash.wrl Description: VRML model
