Bug 583423 - [abrt] crash in paraview-3.6.2-1.fc12: Process /usr/lib64/paraview/paraview-real was killed by signal 11 (SIGSEGV)
[abrt] crash in paraview-3.6.2-1.fc12: Process /usr/lib64/paraview/paraview-r...
Product: Fedora
Classification: Fedora
Component: paraview (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Orion Poplawski
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-18 09:44 EDT by mat.bonfanti
Modified: 2010-04-19 18:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-19 18:28:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (48.45 KB, text/plain)
2010-04-18 09:45 EDT, mat.bonfanti
no flags Details

  None (edit)
Description mat.bonfanti 2010-04-18 09:44:59 EDT
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
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
Comment 1 mat.bonfanti 2010-04-18 09:45:02 EDT
Created attachment 407399 [details]
File: backtrace
Comment 2 Orion Poplawski 2010-04-19 16:53:59 EDT
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 18:28:50 EDT
> 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 18:33:35 EDT
Regardless, paraview should never segfault.  But I'm happy not to spend time tracking down the issue :-).

Note You need to log in before you can comment on or make changes to this bug.