Bug 928629

Summary: [abrt] gnome-abrt-0.2.8-1.fc18: dlmmap_locked: Process /usr/bin/python2.7 was killed by signal 7 (SIGBUS)
Product: [Fedora] Fedora Reporter: shialeweb <daniel>
Component: pythonAssignee: Bohuslav "Slavek" Kabrda <bkabrda>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bkabrda, chris, daniel, dmalcolm, ivazqueznet, jfilak, jonathansteffan, mstuchli, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:ce890b69f908d90ea20d170ce65e58331d6d750f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 09:43:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: xsession_errors none

Description shialeweb 2013-03-28 05:52:45 UTC
Version-Release number of selected component:
gnome-abrt-0.2.8-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        python /usr/bin/gnome-abrt
crash_function: dlmmap_locked
executable:     /usr/bin/python2.7
kernel:         3.8.4-202.fc18.i686
uid:            1000
ureports_counter: 2

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 dlmmap_locked at ../src/closures.c:437
 #1 dlmmap at ../src/closures.c:477
 #2 sys_alloc at ../src/dlmalloc.c:3515
 #3 dlmalloc at ../src/dlmalloc.c:4245
 #4 ffi_closure_alloc at ../src/closures.c:543
 #5 g_callable_info_prepare_closure at girepository/girffi.c:363
 #6 _pygi_make_native_closure at pygi-closure.c:578
 #7 _wrap_pyg_hook_up_vfunc_implementation at gimodule.c:346
 #8 PyCFunction_Call at /usr/src/debug/Python-2.7.3/Objects/methodobject.c:116
 #9 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4098

Comment 1 shialeweb 2013-03-28 05:53:49 UTC
Created attachment 717431 [details]
File: backtrace

Comment 2 shialeweb 2013-03-28 05:53:51 UTC
Created attachment 717432 [details]
File: cgroup

Comment 3 shialeweb 2013-03-28 05:53:52 UTC
Created attachment 717433 [details]
File: core_backtrace

Comment 4 shialeweb 2013-03-28 05:53:55 UTC
Created attachment 717434 [details]
File: dso_list

Comment 5 shialeweb 2013-03-28 05:53:58 UTC
Created attachment 717435 [details]
File: environ

Comment 6 shialeweb 2013-03-28 05:54:00 UTC
Created attachment 717436 [details]
File: limits

Comment 7 shialeweb 2013-03-28 05:54:03 UTC
Created attachment 717437 [details]
File: maps

Comment 8 shialeweb 2013-03-28 05:54:05 UTC
Created attachment 717438 [details]
File: open_fds

Comment 9 shialeweb 2013-03-28 05:54:06 UTC
Created attachment 717439 [details]
File: proc_pid_status

Comment 10 shialeweb 2013-03-28 05:54:08 UTC
Created attachment 717440 [details]
File: var_log_messages

Comment 11 shialeweb 2013-03-28 05:54:10 UTC
Created attachment 717441 [details]
File: xsession_errors

Comment 12 Jakub Filak 2013-08-14 14:53:38 UTC
Thanks for filing this bug report.

Seems like a bug in selinux-policy (see bug #697223, bug #815228). Do you have any AVC similar to some of AVCs in comments of bug #697223?

Comment 13 Jakub Filak 2013-09-19 09:43:55 UTC
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. 

Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.