Bug 593864 – [abrt] crash in ekiga-3.2.6-1.fc12: std::_Rb_tree_increment: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)

Bug 593864 - [abrt] crash in ekiga-3.2.6-1.fc12: std::_Rb_tree_increment: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)

Summary:	[abrt] crash in ekiga-3.2.6-1.fc12: std::_Rb_tree_increment: Process /usr/bin...

Status:	CLOSED DUPLICATE of bug 539541

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	ekiga (Show other bugs)
Sub Component:
Version:	12
Hardware:	x86_64 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Peter Robinson
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:	abrt_hash:887d75ba4659e7c3aa35a4e9e71...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-05-19 17:43 EDT by Fabrício
Modified:	2010-05-23 17:22 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-05-23 17:22:19 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
File: backtrace (48.73 KB, text/plain) 2010-05-19 17:43 EDT, Fabrício	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Fabrício 2010-05-19 17:43:56 EDT

abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: ekiga
component: ekiga
crash_function: std::_Rb_tree_increment
executable: /usr/bin/ekiga
global_uuid: 887d75ba4659e7c3aa35a4e9e719c6f4fb51d14f
kernel: 2.6.32.11-99.fc12.x86_64
package: ekiga-3.2.6-1.fc12
rating: 4
reason: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Turned off ekiga after problems with SIP not working
2.
3.

Comment 1 Fabrício 2010-05-19 17:43:59 EDT

Created attachment 415270 [details]
File: backtrace

Comment 2 Peter Robinson 2010-05-23 17:22:19 EDT


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

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