this is really annoying..
I am getting a segfault with using git version of refpolicy, but using ubuntu's policy I dont get this.
why?
sudo make load (inside refpolicy tree after building)
cy-test/wireshark.pp -i /usr/share/selinux/refpolicy-test/wm.pp -i /usr/share/selinux/refpolicy-test/xen.pp -i /usr/share/selinux/refpolicy-test/xfs.pp -i /usr/share/selinux/refpolicy-test/xguest.pp -i /usr/share/selinux/refpolicy-test/xprint.pp -i /usr/share/selinux/refpolicy-test/xscreensaver.pp -i /usr/share/selinux/refpolicy-test/xserver.pp -i /usr/share/selinux/refpolicy-test/yam.pp -i /usr/share/selinux/refpolicy-test/zabbix.pp -i /usr/share/selinux/refpolicy-test/zarafa.pp -i /usr/share/selinux/refpolicy-test/zebra.pp -i /usr/share/selinux/refpolicy-test/zosremote.pp
make: *** [load] Segmentation fault
dmesg ..:
? 580.904871] wlan1: associated
[ ?584.220325] semodule[7740]: segfault at 0 ip 400dc341 sp bfa26d00 error 4 in libc-2.13.so[40066000+176000]
Justin P. Mattock
On Tue, 8 Nov 2011, Justin Mattock <[email protected]> wrote:
> this is really annoying..
> I am getting a segfault with using git version of refpolicy, but using
> ubuntu's policy I dont get this. why?
Build it with debugging symbols and run it under gdb.
Also this isn't a refpolicy issue, no matter what's wrong with the policy
semodule shouldn't SEGV. There is no excuse for a SEGV, any program which
gives one (*) is buggy and needs to be fixed. Please remove the refpolicy
list from follow-ups.
(*) Except of course for the unusual cases where hardware errors cause
particular programs to SEGV in which case the hardware needs to be
fixed/replaced.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/