From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: setgroups
Date: Mon, 21 Apr 2003 12:20:43 -0400 [thread overview]
Message-ID: <m3el3v95zi.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m3znmnr8yw.fsf@multivac.cwru.edu> (Paul Jarc's message of "Fri, 18 Apr 2003 13:49:53 -0400")
I wrote:
> + result = setgroups (ngroups, groups);
> + free (groups);
> + if (result < 0)
> + SCM_SYSERROR;
Should errno be saved and restored here to avoid interference from
free()? The C standard says: "The value of errno may be set to
nonzero by a library function call whether or not there is an error,
provided the use of errno is not documented in the description of the
function in this International Standard.", and the description of
free() doesn't mention errno. But if we're already ignoring this
issue in the rest of the code, I won't bother. (Or I'll work on a
patch later to address as many instances of the problem as I can
find.)
paul
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-04-21 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3y928ripu.fsf@multivac.cwru.edu>
2003-04-17 22:29 ` setgroups Rob Browning
2003-04-17 22:43 ` setgroups Paul Jarc
2003-04-17 23:10 ` setgroups Marius Vollmer
2003-04-18 3:19 ` setgroups Rob Browning
2003-04-17 23:20 ` setgroups Paul Jarc
2003-04-18 3:34 ` setgroups Rob Browning
2003-04-18 10:31 ` setgroups Marius Vollmer
2003-04-18 15:37 ` setgroups Paul Jarc
2003-04-18 17:38 ` setgroups Paul Jarc
2003-04-18 17:49 ` setgroups Paul Jarc
2003-04-21 16:20 ` Paul Jarc [this message]
2003-04-18 15:41 ` setgroups Rob Browning
2003-04-18 16:00 ` setgroups Paul Jarc
2003-04-18 17:01 ` setgroups Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3el3v95zi.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).