From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: [ SEMANAGE ] More work on policy_components.c
Date: Thu, 20 Oct 2005 13:21:21 -0400 [thread overview]
Message-ID: <4357D211.3090205@cornell.edu> (raw)
In-Reply-To: <1129827334.2375.429.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2005-10-19 at 21:24 -0400, Ivan Gyurdiev wrote:
>
>> This patch makes the commit function shorter, and more intelligent, and
>> implements a lot more of the "merge into base" function (but not all of
>> it). It also adds comments in database.h about the behavior of the
>> add(), modify(), and iterate() functions.
>>
>
> Oops, this one causes memory errors on a semodule -b base.pp (per
> valgrind).
>
That's not possible, because those patches don't touch that code path...
The problem is from earlier patches - you can comment out the init() and
release() code in direct_api.c - should eliminate any bugs. I didn't
think something as simple would be broken. I'll fix the problem a bit
later today...
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2005-10-20 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 1:24 [ SEMANAGE ] More work on policy_components.c Ivan Gyurdiev
2005-10-20 15:05 ` Stephen Smalley
2005-10-20 17:12 ` [ SEMANAGE ] More dbase things Ivan Gyurdiev
2005-10-20 17:58 ` Stephen Smalley
2005-10-20 16:55 ` [ SEMANAGE ] More work on policy_components.c Stephen Smalley
2005-10-20 17:04 ` Stephen Smalley
2005-10-20 17:21 ` Ivan Gyurdiev [this message]
2005-10-20 17:11 ` Stephen Smalley
2005-10-20 17:16 ` Stephen Smalley
2005-10-20 17:30 ` Ivan Gyurdiev
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=4357D211.3090205@cornell.edu \
--to=ivg2@cornell.edu \
--cc=sds@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.