Bug 680496

Summary: [abrt] mesa-demos-7.10-4.20101028.fc15: LinkShaders: Process /usr/lib64/mesa/mandelbrot was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Michal Hlavinka <mhlavink>
Component: mesa-demosAssignee: Jérôme Glisse <jglisse>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: airlied, ajax, jglisse
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:48c92e2b25c5ef909a8fa5ff96cf65724d74eeb1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:07:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Michal Hlavinka 2011-02-25 18:01:58 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 6332 bytes
cmdline: ./mandelbrot
component: mesa-demos
Attached file: coredump, 11997184 bytes
crash_function: LinkShaders
executable: /usr/lib64/mesa/mandelbrot
kernel: 2.6.38-0.rc6.git2.1.fc15.x86_64
package: mesa-demos-7.10-4.20101028.fc15
rating: 4
reason: Process /usr/lib64/mesa/mandelbrot was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1298656097
uid: 500

comment
-----
kernel-2.6.38-0.rc6.git2.1.fc15.x86_64
xorg-x11-drv-ati-6.14.0-2.20110204gita27b5dbd9.fc15.x86_64
mesa-*-7.10-0.27.fc15.x86_64

How to reproduce
-----
1.just start
2.
3.
Comment 1 Michal Hlavinka 2011-02-25 18:02:00 UTC 
Created attachment 481050 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 16:07:57 UTC 
Backtrace analysis found this bug to be similar to bug #680494, closing as duplicate.

Bugs which were found to be similar to this bug: bug #680494, bug #680495, bug #680499, bug #680501

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 680494 ***