MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014203ParaView(No Category)public2013-08-01 11:412016-08-12 09:59
ReporterJan Knaup 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version4.0 
Target VersionFixed in Version 
ProjectTBD
Topic Name
Typecrash
Summary0014203: Crash when trying to read XMOL .xyz files: cannot find elements.xml
DescriptionFound in ParaView-4.0.1-Linux-64bit, installed from binary distribution from paraview.org.

When trying to open the enclosed XMOL .xyz file or any other file of the same type, the program crashed with the stack trace appended below. Apparently a file "elements.xml" is searched in a hard-coded absolute location instead of relative to the installation directory.

Stack trace:
ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Domains/Chemistry/vtkBlueObeliskDataParser.cxx, line 68
vtkBlueObeliskDataParser (0x3196470): Cannot find elements.xml. Checked /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/install//vtkChemistry/vtkBODRData and /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Domains/Chemistry


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/XMLParser/vtkXMLParser.cxx, line 382
vtkBlueObeliskDataParser (0x3196470): Parse() called with no Stream set.


Segmentation fault (core dumped)
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files? trajectory.0000000000.xyz (5,613) 2013-08-01 11:41
https://www.vtk.org/Bug/file/9492/trajectory.0000000000.xyz
Issue History
Date ModifiedUsernameFieldChange
2013-08-01 11:41Jan KnaupNew Issue
2013-08-01 11:41Jan KnaupFile Added: trajectory.0000000000.xyz
2016-08-12 09:59Kitware RobotNote Added: 0038429
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0038429)
Kitware Robot   
2016-08-12 09:59   
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.