All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	Joshua Brindle <jbrindle@tresys.com>
Subject: Re: [SEMANAGE][UTILS] Use PyList in bindings
Date: Thu, 02 Feb 2006 16:16:10 -0500	[thread overview]
Message-ID: <43E2769A.8040601@cornell.edu> (raw)
In-Reply-To: <43E26F62.7010400@cornell.edu>

[-- Attachment #1: Type: text/plain, Size: 192 bytes --]

On the same note, this patch fixes a memory leak in the wrapper for 
things like:
semanage_context_to_string.

It's most likely language-portable (SWIG_FromCharPtr marks argument as 
const).


[-- Attachment #2: libsemanage.python_string_leak.diff --]
[-- Type: text/x-patch, Size: 433 bytes --]

diff -Naurp --exclude-from excludes old/libsemanage/src/semanageswig.i new/libsemanage/src/semanageswig.i
--- old/libsemanage/src/semanageswig.i	2006-02-02 16:12:36.000000000 -0500
+++ new/libsemanage/src/semanageswig.i	2006-02-02 15:53:40.000000000 -0500
@@ -69,6 +69,7 @@
 
 %typemap(argout) char** {
 	$result = t_output_helper($result, SWIG_FromCharPtr(*$1));
+	free(*$1);
 }
 
 %typemap(in, numinputs=0) char ***(char **temp) {

  reply	other threads:[~2006-02-02 21:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02 20:45 [SEMANAGE][UTILS] Use PyList in bindings Ivan Gyurdiev
2006-02-02 21:16 ` Ivan Gyurdiev [this message]
2006-02-03 14:00 ` Stephen Smalley
2006-02-03 14:36   ` Joshua Brindle
2006-02-14 10:59 ` Ivan Gyurdiev
2006-02-14 12:08   ` Move python bindings into semanageswig_python.i Ivan Gyurdiev
2006-02-14 18:51     ` Improve bindings, add PyList(String) for roles array Ivan Gyurdiev
2006-02-14 20:12       ` Stephen Smalley
2006-02-14 19:01     ` Move python bindings into semanageswig_python.i Stephen Smalley
2006-02-14 18:57   ` [SEMANAGE][UTILS] Use PyList in bindings Stephen Smalley

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=43E2769A.8040601@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=jbrindle@tresys.com \
    --cc=sds@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.