Summary: SELinux is preventing /usr/bin/gdb "write" access on gdb. Detailed Description: SELinux denied access requested by gdb. It is not expected that this access is required by gdb and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:usr_t:s0 Target Objects gdb [ dir ] Source gdb Source Path /usr/bin/gdb Port <Unknown> Host (removed) Source RPM Packages gdb-7.0-3.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-41.fc12 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64 Alert Count 2 First Seen Wed 18 Nov 2009 07:45:48 AM CET Last Seen Wed 18 Nov 2009 07:45:48 AM CET Local ID 215663bf-5708-4102-91ec-1b591458db8e Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1258526748.233:43685): avc: denied { write } for pid=2496 comm="gdb" name="gdb" dev=dm-1 ino=62553 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usr_t:s0 tclass=dir node=(removed) type=SYSCALL msg=audit(1258526748.233:43685): arch=c000003e syscall=2 success=no exit=-13 a0=7fffb23e7fa0 a1=2c1 a2=81ed a3=7fc18c417ad0 items=0 ppid=2495 pid=2496 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="gdb" exe="/usr/bin/gdb" subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) Hash String generated from selinux-policy-3.6.32-41.fc12,catchall,gdb,xdm_t,usr_t,dir,write audit2allow suggests: #============= xdm_t ============== allow xdm_t usr_t:dir write;
I believe this is caused by gdb trying to write to the /usr/share/gdb/python/gdb directory. Do you have some python scripts here without pyo and pyc files?
No, all .pyo/.pyc files are present there as built by the python .spec rules.
The NEEDINFO was from the reporter I see, sorry. +`rpm -V gdb' output would be ale useful.
Yes, I checked on my machine and the pyc and pyo files were there. But that is the most likely cause.
hello everybody, i'm new to linux and all, just got F12 and wanted to check it out. i don't know what info you need or how to get them, any help tutorial would be appreciated. reason for the report is that i saw somewhere i should file a bug report, so i did. ty in advance
Just tell us what the contents of /usr/share/gdb/python/gdb is ls -l /usr/share/gdb/python/gdb And attach the output of rpm -qV gdb
*** Bug 542014 has been marked as a duplicate of this bug. ***
*** Bug 551071 has been marked as a duplicate of this bug. ***
This Bug has nothing to do with gdb. gdb is just using python binding. This is an issue of python (or python rpm support scripts) vs. selinux.
gdb is shipping py files without the pyc/pyo files.
*** Bug 551904 has been marked as a duplicate of this bug. ***
(In reply to comment #10) > gdb is shipping py files without the pyc/pyo files. "gdb" does not. But "glib2-devel" does: /usr/share/glib-2.0/gdb/glib.py /usr/share/glib-2.0/gdb/gobject.py due to: %exclude %{_datadir}/glib-2.0/gdb/*.pyo %exclude %{_datadir}/glib-2.0/gdb/*.pyc Present in: glib2-2.22.3-2.fc12
*** This bug has been marked as a duplicate of bug 528554 ***