From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: secilc: segfault on what should be "Recursive block call found"?
Date: Sat, 12 Sep 2015 14:53:22 +0200 [thread overview]
Message-ID: <20150912125321.GB4006@x250> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- ----- Forwarded message from Dominick Grift <dac.override@gmail.com> -----
Date: Sat, 12 Sep 2015 14:51:22 +0200
From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gove
Subject: secilc: segfault on what should be "Recursive block call found"?
User-Agent: Every email client sucks, this one just sucks less.
I am knee-deep in namespaces and hitting all kinds of exotic challenges
I had a macro with the same name as a macro call in it, like:
(in bla
(macro foo ((type ARG1))
call foo (ARG1)))
secilc helpfully threw a message telling me:
Recursive macro call found
Failed to compile cildb: -1
Great. after a short struggle i managed to locate the issue (unfortunately
secilc was not more specific as to the location of the issue)
Now i am hitting what seems to be a similar issue to the above. except
that in this case its not about macros but about block
consider:
(in bla
(block foo_blk
(blockabstract foo_blk)
(blockinherit foo_blk))
In this case, though secilc segfaults, instead of telling me:
Recursive block call found
Failed to compile cildb: -1
this is just theory though... but i suspect the above is true
- --
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
https://sks-keyservers.net/pks/lookup?op=get&search=0x314883A202DFF788
Dominick Grift
- ----- End forwarded message -----
- --
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
iQGcBAEBCgAGBQJV9CA8AAoJENAR6kfG5xmcbWoL/1bxjVcZTjSGEwvOJJL0HDSi
r1zyPy/o/9cjAE1Zw3uVBxnzESwpb1nWepQPYhkJ8d79tzS4vgV14MeEw3RHpboF
9eKJg5UvmhCjMk5H+Kjrg6wuAvK+4wqTHTY0IMNjkRrvzQ2PYNWM/kmJedAqO3SE
4R2uTw1H0JIx4+w+ZcQZwOP1oxYjdJAJCrvryY3I6FGPuhWB+yX5OIJ48oSHcbJR
WjYlKvYFuK2obAYlGcLBdf1Rdl4K5bCUUMm+rgv5r7cQnd8tlnqnx9rx8DKv0tt+
V5OZc4Kok3m4+U/mTNl/mwTwHh9muen9bw7AfJ8R1OaoW9TJmefKHETvqMVLv3MF
fEma8v+TZL+UXxE45tCYTeezm8YhIWeGJ9Xi6yTkDkAsNtUrW3aL9/R6tgimuIwF
aA3lsgHvm9fvBHRTAK/Db6OygDp1eedF0t/OMZHGhW4/bmLSwYOt3vnlE0NTJHk9
Je2lwOCHhnBXxnLfCUrUJMVdH1N5K91cI2ie6KBC5A==
=CkY3
-----END PGP SIGNATURE-----
next reply other threads:[~2015-09-12 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 12:53 Dominick Grift [this message]
2015-09-14 13:24 ` secilc: segfault on what should be "Recursive block call found"? Dominick Grift
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=20150912125321.GB4006@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.