Bug 583423

Summary: [abrt] crash in paraview-3.6.2-1.fc12: Process /usr/lib64/paraview/paraview-real was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mat.bonfanti
Component: paraviewAssignee: Orion Poplawski <orion>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: orion, pertusus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:72377ad022f38b3e1322953319feaa08b2af7bff
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-19 22:28:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description mat.bonfanti 2010-04-18 13:44:59 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/paraview/paraview-real --data=Barrierbridge_Qhcp.vtk
component: paraview
executable: /usr/lib64/paraview/paraview-real
kernel: 2.6.32.11-99.fc12.x86_64
package: paraview-3.6.2-1.fc12
rating: 4
reason: Process /usr/lib64/paraview/paraview-real was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.make contour plot
2.
3.
Comment 1 mat.bonfanti 2010-04-18 13:45:02 UTC 
Created attachment 407399 [details]
File: backtrace
Comment 2 Orion Poplawski 2010-04-19 20:53:59 UTC 
Can you attach the Barrierbridge_Qhcp.vtk data file, or if it is too large, post a url for it?
Comment 3 mat.bonfanti 2010-04-19 22:28:50 UTC 
> Can you attach the Barrierbridge_Qhcp.vtk data file, or if it is too large,
> post a url for it?    

I found the error in the file Barrierbridge_Qhcp.vtk.
It was my fault... sorry.(In reply to comment #2)
Comment 4 Orion Poplawski 2010-04-19 22:33:35 UTC 
Regardless, paraview should never segfault.  But I'm happy not to spend time tracking down the issue :-).