From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: secilc: segfault on what should be "Recursive block call found"?
Date: Mon, 14 Sep 2015 15:24:05 +0200 [thread overview]
Message-ID: <20150914132404.GA15129@x250> (raw)
In-Reply-To: <20150912125321.GB4006@x250>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
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)
- --
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
https://sks-keyservers.net/pks/lookup?op=get&search=0x314883A202DFF788
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCgAGBQJV9spwAAoJENAR6kfG5xmcx4kL/i4JxNAuu3csjwi2RK+CsbNY
1E/Bqwuo4YARC5pXdxHRuOd6NPeJYZg1ZY0zB44qDN17iMGfjzcI5zCfO8HDerov
HkoG/h462Z2JC/qdu0hyrhic5tY1t+kh5l4cIHVsxPfbvpDv27+UKRa4ufGzpqTd
moqXlh84T/6IOVhEH9bHF5gp5vFRyXkM5B8Fb3p6Q7pvVwtxDn2js3YljcrxBrOo
6NHZ4BrLSw4sJgfllnVt3HzwucrruyMZwR1F7aB5b+sErsFRV/akl2Bq+ULf1uDU
EVhblfIJyy2HvJkzHKNxpOIS+iYb7GMSmdZ4CWXIMTwewRekmHjvwhzXbahjrM53
bv3KK7J1Z3YF69ORzonbDLIzCHWuXfoDCmFxEseG19yxpyhPgHnfOwrwIBuTUeD4
b/bRUDmKwI5qGDjFQu9fCyNRDQ9nLENLHI3lqBeFYP+7dqPuQIfLOHjAnjV28J2a
gAJFv6eFBsItDQmF5BxuKeA6EdRGpv6IUu8emw04+A==
=4D0w
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-09-14 13:24 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 [this message]
2015-09-14 13:33 ` Steve Lawrence
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=20150914132404.GA15129@x250 \
--to=dac.override@gmail.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.