From: Dominick Grift <dac.override@gmail.com>
To: James Carter <jwcart2@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: secilc: in segfault
Date: Thu, 3 Sep 2015 15:20:42 +0200 [thread overview]
Message-ID: <20150903132041.GD2118@x250> (raw)
In-Reply-To: <55E83A89.5010208@tycho.nsa.gov>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
On Thu, Sep 03, 2015 at 08:18:17AM -0400, James Carter wrote:
> On 09/03/2015 05:48 AM, Dominick Grift wrote:
> >Anyone tried "secilc test/in_test.cil" lately? It dumps core here.
> >
> >$ secilc test/in_test.cil
> >Segmentation fault (core dumped)
> >
> >
>
> It works for me for the current master branch of SELinux userspace installed
> locally. What version are you using?
>
> Jim
>
Ok so that turns out to be a bug in Fedora. However.
I can still get secilc to segfault on "in". I wonder if the following is
or should be supported:
The scenario is: I want to simplify my macros by using
blockabstracts/inherits to provide a single point of failure
As a matter of test i made these two changes:
https://github.com/DefenSec/dssp/commit/85ba6f1848118e16b5544052dc5764663b272262
https://github.com/DefenSec/dssp-contrib/commit/77442e1e4658df99d1ce74732338a9c4ad80a6a3
However this makes secilc segfault, and i do not see why.
I first thought it was because i was using "ARG1" in the blockabstract
(see first commit). However that seems to not be the case.
I am left wondering: what am i doing wrong here (obviously secilc should
not segfault nevertheless)
--
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
http://keys.gnupg.net/pks/lookup?op=vindex&search=0x314883A202DFF788
Dominick Grift
[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]
next prev parent reply other threads:[~2015-09-03 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 9:48 secilc: in segfault Dominick Grift
2015-09-03 12:18 ` James Carter
2015-09-03 12:32 ` Dominick Grift
2015-09-03 12:40 ` Dominick Grift
2015-09-03 12:53 ` Petr Lautrbach
2015-09-03 13:04 ` Dominick Grift
2015-09-03 13:20 ` Dominick Grift [this message]
2015-09-09 20:17 ` James Carter
2015-09-09 20:45 ` Dominick Grift
2015-09-10 7:08 ` Dominick Grift
2015-09-10 13:37 ` Steve Lawrence
2015-09-11 16:02 ` 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=20150903132041.GD2118@x250 \
--to=dac.override@gmail.com \
--cc=jwcart2@tycho.nsa.gov \
--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.