From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>,
Karl MacMillan <kmacmillan@tresys.com>
Subject: Re: [ SEMANAGE ] Replace semanage debugging system
Date: Tue, 11 Oct 2005 10:15:14 -0400 [thread overview]
Message-ID: <434BC8F2.8040502@cornell.edu> (raw)
In-Reply-To: <1129037671.3308.84.camel@moss-spartans.epoch.ncsc.mil>
> OTOH, __func__ is not known to older versions of gcc, and we already
> build with -D_GNU_SOURCE.
>
How much older? From the gcc webpage, I see it supported for 3.0+.
IMHO we should compile against a standard, not against a compiler..
> An obvious concern about the new msg_write function is that it requires
> memory allocation itself. Thus, on a memory allocation failure in the
> caller, we might easily end up dropping the out of memory error message
> due to lack of available memory at this point.
>
By the way, does the printf family require such a memory allocation?
--
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-11 14:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 6:59 [ SEMANAGE ] Replace semanage debugging system Ivan Gyurdiev
2005-10-11 9:03 ` [ SEPOL ] Another " Ivan Gyurdiev
2005-10-11 14:45 ` Stephen Smalley
2005-10-11 15:11 ` Ivan Gyurdiev
2005-10-11 15:15 ` Stephen Smalley
2005-10-11 15:51 ` Stephen Smalley
2005-10-11 13:34 ` [ SEMANAGE ] Replace semanage " Stephen Smalley
2005-10-11 14:06 ` Stephen Smalley
2005-10-11 14:29 ` Ivan Gyurdiev
2005-10-11 14:30 ` Stephen Smalley
2005-10-11 14:57 ` Ivan Gyurdiev
2005-10-11 14:46 ` Stephen Smalley
2005-10-11 15:18 ` Ivan Gyurdiev
2005-10-11 15:19 ` Stephen Smalley
2005-10-11 16:35 ` Ivan Gyurdiev
2005-10-11 17:27 ` Ivan Gyurdiev
2005-10-11 17:23 ` Stephen Smalley
2005-10-11 14:15 ` Ivan Gyurdiev [this message]
2005-10-11 14:24 ` 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=434BC8F2.8040502@cornell.edu \
--to=ivg2@cornell.edu \
--cc=dwalsh@redhat.com \
--cc=kmacmillan@tresys.com \
--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.