Bug 583423 - [abrt] crash in paraview-3.6.2-1.fc12: Process /usr/lib64/paraview/paraview-real was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in paraview-3.6.2-1.fc12: Process /usr/lib64/paraview/paraview-r...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: paraview
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:72377ad022f38b3e1322953319f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-18 13:44 UTC by mat.bonfanti
Modified: 2010-04-19 22:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-19 22:28:50 UTC
Type: ---
Embargoed:

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

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 :-).
Note You need to log in before you can comment on or make changes to this bug.