Bug 962369

Summary: [abrt] policycoreutils-2.1.13-59.fc18: policydb_destroy: Process /usr/sbin/semodule was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Frank Murphy <frankly3d>
Component: policycoreutilsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6eacaa76bd9315826487e07195865eea1f0f24ee
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-11 19:11:48 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

Description Frank Murphy 2013-05-13 09:49:35 UTC 
Description of problem:
I was running a local fix from sealert # semodule -i F18lightdm01.pp
Segmentation fault (core dumped)

Version-Release number of selected component:
policycoreutils-2.1.13-59.fc18

Additional info:
reporter:       libreport-2.1.4.8.gd975
backtrace_rating: 4
cmdline:        semodule -i F18lightdm01.pp
crash_function: policydb_destroy
executable:     /usr/sbin/semodule
kernel:         3.9.2-0.rc1.200.fc18.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #2 policydb_destroy at policydb.c:1337
 #3 sepol_policydb_free_internal at policydb_public.c:82
 #4 semanage_direct_commit at direct_api.c:1007
 #5 semanage_commit at handle.c:485
Comment 1 Frank Murphy 2013-05-13 09:49:38 UTC 
Created attachment 747151 [details]
File: backtrace
Comment 2 Frank Murphy 2013-05-13 09:49:41 UTC 
Created attachment 747152 [details]
File: cgroup
Comment 3 Frank Murphy 2013-05-13 09:49:43 UTC 
Created attachment 747153 [details]
File: core_backtrace
Comment 4 Frank Murphy 2013-05-13 09:49:45 UTC 
Created attachment 747154 [details]
File: dso_list
Comment 5 Frank Murphy 2013-05-13 09:49:47 UTC 
Created attachment 747155 [details]
File: environ
Comment 6 Frank Murphy 2013-05-13 09:49:49 UTC 
Created attachment 747156 [details]
File: limits
Comment 7 Frank Murphy 2013-05-13 09:49:52 UTC 
Created attachment 747157 [details]
File: maps
Comment 8 Frank Murphy 2013-05-13 09:49:54 UTC 
Created attachment 747158 [details]
File: open_fds
Comment 9 Frank Murphy 2013-05-13 09:49:56 UTC 
Created attachment 747159 [details]
File: proc_pid_status
Comment 10 Frank Murphy 2013-05-13 09:49:58 UTC 
Created attachment 747160 [details]
File: var_log_messages
Comment 11 Daniel Walsh 2013-05-13 15:37:20 UTC 
Was this done on a limited memory system?
Comment 12 Frank Murphy 2013-05-13 16:00:03 UTC 
8 gb ram, quad 2 core
Comment 13 Daniel Walsh 2013-05-13 17:09:17 UTC 
That looks fine.  Is this repeatable?
Comment 14 Frank Murphy 2013-05-14 11:01:22 UTC 
(In reply to comment #13)
> That looks fine.  Is this repeatable?

Haven't managed to cause another crash, even with Azureus\Vuze running.
Comment 15 Daniel Walsh 2013-07-11 19:11:48 UTC 
Ok I am going to close with Insufficient data, since I can not find the problem.

Reopen if it happens again