Bug 684330 - [abrt] anjuta-1:2.32.1.1-1.fc14: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Summary: [abrt] anjuta-1:2.32.1.1-1.fc14: Process /usr/bin/anjuta was killed by signal...
Keywords:
Status: CLOSED DUPLICATE of bug 704024
Alias: None
Product: Fedora
Classification: Fedora
Component: anjuta
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:49429cc570b80a776c5f09f6f08...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 20:08 UTC by luxyrybugs
Modified: 2012-03-21 16:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:42:07 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (42.20 KB, text/plain)
2011-03-11 20:08 UTC, luxyrybugs 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description luxyrybugs 2011-03-11 20:08:35 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 43212 bytes
cmdline: anjuta --no-splash --no-client file:///home/mag/NetBeansProjects/sfmlTest/sfmlTest.anjuta
component: anjuta
Attached file: coredump, 2327269376 bytes
crash_function: npw_property_set_value_from_widget
executable: /usr/bin/anjuta
kernel: 2.6.35.11-83.fc14.x86_64
package: anjuta-1:2.32.1.1-1.fc14
rating: 4
reason: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1.adding new project 
time: 1299873642
uid: 500
Comment 1 luxyrybugs 2011-03-11 20:08:39 UTC 
Created attachment 483806 [details]
File: backtrace
Comment 2 Johannes Schmid 2011-03-11 20:40:18 UTC 
Could you please be a bit more specific about the steps to reproduce this?

Thanks!
Comment 3 luxyrybugs 2011-03-12 12:10:20 UTC 
new project -> standard c++ -> [basic info], next -> [project options] select 3x YES, next -> don't select any packet, next -> !! BOOM !!
Comment 4 abrt-bot 2012-03-21 16:42:07 UTC 
Backtrace analysis found this bug to be similar to bug #704024, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 704024 ***
Note You need to log in before you can comment on or make changes to this bug.