On 12/01/2016 01:16 PM, Vit Mojzis wrote:
> Hi,
>
> I hit a dead end while trying to revive sepolicy gui after sepolicy
> started using SETools 4.
> I keep getting the following segfault in SETools 4 (libqpol).
Can you specify what version/branch/commit of setools you built?
And what version of s
Hi,
I hit a dead end while trying to revive sepolicy gui after sepolicy
started using SETools 4.
I keep getting the following segfault in SETools 4 (libqpol).
Thread 1 "python" received signal SIGSEGV, Segmentation fault.
0x7fffeb07b238 in filename_trans_state_next (iter=0x578b5cf0)