MantisBT - ParaView
View Issue Details
0008071ParaView(No Category)public2008-11-10 06:382016-08-12 09:57
dh 
Kitware Robot 
normalcrashalways
closedmoved 
 
 
0008071: crash when reading vrml 2 file
paraview crashes reguraly when reading vrml2 files. Example is attached.

> script
Script started, file is typescript
sh-3.2$ gdb /tmp/paraview-3.4.0-Linux-x86_64/bin/paraview
GNU gdb Red Hat Linux (6.5-37.el5_2.2rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".

(gdb) run
Starting program: /tmp/paraview-3.4.0-Linux-x86_64/bin/paraview
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x00002b146c9cb4b4 in ?? ()
(gdb) Quit
(gdb) quit
The program is running. Exit anyway? (y or n) y
sh-3.2$ exit
exit
Script done, file is typescript
No tags attached.
gz Explorer.k.small.wrl.gz (1,214,359) 2008-11-10 06:38
https://www.vtk.org/Bug/file/6839/Explorer.k.small.wrl.gz
Issue History
2008-11-10 06:38dhNew Issue
2008-11-10 06:38dhFile Added: Explorer.k.small.wrl.gz
2009-02-17 14:56Utkarsh AyachitCategory3.4 => 3.8
2009-05-13 13:41Utkarsh AyachitTarget Version => 3.8
2011-06-16 13:10Zack GalbreathCategory => (No Category)
2016-08-12 09:57Kitware RobotNote Added: 0037602
2016-08-12 09:57Kitware RobotStatusexpired => closed
2016-08-12 09:57Kitware RobotResolutionopen => moved
2016-08-12 09:57Kitware RobotAssigned To => Kitware Robot

Notes
(0037602)
Kitware Robot   
2016-08-12 09:57   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.