Bug 887047 - [abrt] bluefish-2.2.3-1.fc17: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
Summary: [abrt] bluefish-2.2.3-1.fc17: Process /usr/bin/bluefish was killed by signal ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bluefish
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a8787284c08d2a2e7c11287ba13...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-13 22:48 UTC by Roman Melihhov
Modified: 2012-12-17 10:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-17 10:38:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: environ (1.64 KB, text/plain)
2012-12-13 22:48 UTC, Roman Melihhov
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-13 22:48 UTC, Roman Melihhov
no flags Details
File: backtrace (70.98 KB, text/plain)
2012-12-13 22:48 UTC, Roman Melihhov
no flags Details
File: cgroup (128 bytes, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details
File: smolt_data (2.85 KB, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details
File: executable (17 bytes, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details
File: maps (44.73 KB, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details
File: dso_list (8.52 KB, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details
File: proc_pid_status (930 bytes, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details
File: open_fds (682 bytes, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details
File: var_log_messages (459 bytes, text/plain)
2012-12-13 22:49 UTC, Roman Melihhov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 690209 0 None None None Never

Description Roman Melihhov 2012-12-13 22:48:52 UTC
Version-Release number of selected component:
bluefish-2.2.3-1.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        bluefish /home/roman/4modelsdotinfo.elgg/elgg-1.8.6/engine/settings.example.php
kernel:         3.6.9-2.fc17.x86_64

Comment 1 Roman Melihhov 2012-12-13 22:48:54 UTC
Created attachment 663225 [details]
File: environ

Comment 2 Roman Melihhov 2012-12-13 22:48:56 UTC
Created attachment 663226 [details]
File: limits

Comment 3 Roman Melihhov 2012-12-13 22:48:58 UTC
Created attachment 663227 [details]
File: backtrace

Comment 4 Roman Melihhov 2012-12-13 22:49:00 UTC
Created attachment 663228 [details]
File: cgroup

Comment 5 Roman Melihhov 2012-12-13 22:49:02 UTC
Created attachment 663229 [details]
File: smolt_data

Comment 6 Roman Melihhov 2012-12-13 22:49:04 UTC
Created attachment 663230 [details]
File: executable

Comment 7 Roman Melihhov 2012-12-13 22:49:06 UTC
Created attachment 663231 [details]
File: maps

Comment 8 Roman Melihhov 2012-12-13 22:49:08 UTC
Created attachment 663232 [details]
File: dso_list

Comment 9 Roman Melihhov 2012-12-13 22:49:10 UTC
Created attachment 663233 [details]
File: proc_pid_status

Comment 10 Roman Melihhov 2012-12-13 22:49:12 UTC
Created attachment 663234 [details]
File: open_fds

Comment 11 Roman Melihhov 2012-12-13 22:49:14 UTC
Created attachment 663235 [details]
File: var_log_messages

Comment 12 Paul Howarth 2012-12-14 13:31:05 UTC
Reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=690209

Comment 13 Paul Howarth 2012-12-17 10:38:16 UTC
Upstream says:

  "the backtrace seems to indicate that there is some memory corruption
   somewhere else. Without more information there is no way to find out
   what is causing this. I'm closing this on this end, I suggest you do
   the same on the redhat bugzilla until the reporter provides more
   information how to reproduce this."

I'll do as upstream suggests and close this; please re-open if you have any more information you can add about this crash, or better still, a way of reproducing it.


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