All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: selinux@tycho.nsa.gov
Subject: Memory leaks
Date: Thu, 29 Sep 2005 23:29:59 -0400	[thread overview]
Message-ID: <433CB137.9000002@cornell.edu> (raw)
In-Reply-To: <433CA7CA.6000207@cornell.edu>

Here's a couple of memory leaks, if anyone wants to investigate. If not, 
I'll take a look at them eventually. The first one is my fault. The 
second one isn't. The main binary I used doesn't bother freeing things, 
but I think valgrind is smart enough to recognize that, and those are 
real leaks.

==10639== 8 bytes in 2 blocks are definitely lost in loss record 4 of 74
==10639==    at 0x1B9017F2: malloc (vg_replace_malloc.c:149)
==10639==    by 0x805313F: sepol_user_get_roles (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==    by 0x80493D9: main (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==
==10639==
==10639== 64 (32 direct, 32 indirect) bytes in 2 blocks are definitely 
lost in loss record 21 of 74
==10639==    at 0x1B9017F2: malloc (vg_replace_malloc.c:149)
==10639==    by 0x805C46A: ebitmap_read (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==    by 0x804EA64: mls_read_range_helper (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==    by 0x805044D: user_read (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==    by 0x8051923: policydb_read (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==    by 0x8051F50: policydb_from_image (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==    by 0x804AFE9: sepol_genusers (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)
==10639==    by 0x8049291: main (in 
/home/phantom/rpmbuild/BUILD/test.mls/test)




--
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.

  parent reply	other threads:[~2005-09-30  3:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30  2:49 [ 1/9 ] [ SEPOL ] Eliminate struct pointer typedefs Ivan Gyurdiev
2005-09-30  2:52 ` [ 2/9 ] [ SEMANAGE ] Restore sepol compatibility Ivan Gyurdiev
2005-09-30  2:55 ` [ 3/9 ] [ SEMANAGE ] Rename files Ivan Gyurdiev
2005-09-30  3:02 ` [ 4/9 ] [ SEMANAGE ] Database initialization Stage 1 Ivan Gyurdiev
2005-09-30 18:42   ` Ivan Gyurdiev
2005-09-30  3:04 ` [ 5/9 ] [ SEMANAGE ] Change database to singly-linked list Ivan Gyurdiev
2005-09-30  3:07 ` [ 6/9 ] [ SEMANAGE ] Database Initialization Stage 2 Ivan Gyurdiev
2005-09-30  3:14 ` [ 7/9 ] [ SEMANAGE ] Backend separation (Init 3) Ivan Gyurdiev
2005-09-30 13:45   ` Ivan Gyurdiev
2005-09-30  3:16 ` [ 8/9 ] [ SEMANAGE ] Eliminate struct pointer typedefs Ivan Gyurdiev
2005-09-30  3:26 ` [ 9/9 ] [ SEPOL ] User list function, Bugfixes Ivan Gyurdiev
2005-09-30  3:29 ` Ivan Gyurdiev [this message]
2005-09-30  6:01   ` Memory leaks Ivan Gyurdiev
2005-09-30  3:34 ` Linking to semanage Ivan Gyurdiev
2005-09-30  5:56   ` Ivan Gyurdiev
  -- strict thread matches above, loose matches on Subject: below --
2005-07-06  2:52 memory leaks Lee Revell
2005-07-06  8:06 ` Clemens Ladisch
2005-07-06 17:34   ` Lee Revell

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=433CB137.9000002@cornell.edu \
    --to=ivg2@cornell.edu \
    --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.