Re: secilc: segfault on what should be "Recursive block call found"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/14/2015 09:24 AM, Dominick Grift wrote:
> On Sat, Sep 12, 2015 at 02:53:21PM +0200, Dominick Grift wrote:
> <snip>
> 
>> secilc helpfully threw a message telling me:
> 
>>     Recursive macro call found
>>     Failed to compile cildb: -1
> 
> 
> The above is an example for how error message should *not* look. Here is
> an example of how they *should* look:
> 
> macro statement is not allowed in optionals (/run/user/1000/dssp/sources/modules/contrib/system/usersubj/macros.cil:819)
> 


The original issue was with recursive blockinherits. Should have a patch
out shortly. Will also improve the error message for macros (and
blockinherits) to show a trace of where the recursion came form.

- Steve
_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.



[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux