Bug 856224 - [abrt] gstreamer-0.10.31-1.fc14: vasprintf: Process /usr/libexec/gstreamer-0.10/gst-plugin-scanner was killed by signal 11 (SIGSEGV)
Summary: [abrt] gstreamer-0.10.31-1.fc14: vasprintf: Process /usr/libexec/gstreamer-0....
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Benjamin Otte
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9fcbfc5104be111ead5bbeec329...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-11 13:36 UTC by william brownell
Modified: 2016-02-10 14:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-26 09:30:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (69.26 KB, text/plain)
2012-09-11 13:36 UTC, william brownell 		no flags Details
View All

Description william brownell 2012-09-11 13:36:21 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 70926 bytes
cmdline: /usr/libexec/gstreamer-0.10/gst-plugin-scanner -l
component: gstreamer
Attached file: coredump, 5509120 bytes
crash_function: vasprintf
executable: /usr/libexec/gstreamer-0.10/gst-plugin-scanner
kernel: 2.6.35.14-106.fc14.i686
package: gstreamer-0.10.31-1.fc14
rating: 4
reason: Process /usr/libexec/gstreamer-0.10/gst-plugin-scanner was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1347370106
uid: 504

How to reproduce
-----
1.i dont know
2.
3.
Comment 1 william brownell 2012-09-11 13:36:25 UTC 
Created attachment 611771 [details]
File: backtrace
Comment 2 Jan Kurik 2015-12-22 11:31:39 UTC 
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide.

Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.
Note You need to log in before you can comment on or make changes to this bug.