From: Steve Lawrence <slawrence@tresys.com>
To: <selinux@tycho.nsa.gov>
Subject: Re: secilc: segfault on what should be "Recursive block call found"?
Date: Mon, 14 Sep 2015 09:33:31 -0400 [thread overview]
Message-ID: <55F6CCAB.6030105@tresys.com> (raw)
In-Reply-To: <20150914132404.GA15129@x250>
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
next prev parent reply other threads:[~2015-09-14 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 12:53 secilc: segfault on what should be "Recursive block call found"? Dominick Grift
2015-09-14 13:24 ` Dominick Grift
2015-09-14 13:33 ` Steve Lawrence [this message]
2015-09-14 14:12 ` Dominick Grift
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F6CCAB.6030105@tresys.com \
--to=slawrence@tresys.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.