From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: setgroups
Date: 18 Apr 2003 12:31:57 +0200 [thread overview]
Message-ID: <874r4w85b6.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87u1cwcwcq.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> I might add a
>
> scm_remember_upto_here_1 (group_vec);
>
> here just to be safe, but that might be overkill, depending on what
> SCM_VECTOR_REF does.
The scm_remember_upto_here is not necessary because SCM_VECTOR_REF
returns a SCM, which is properly protected by the conservative
scanning. Had you used SCM_VELTS, then you would need the
scm_remember_upto_here since SCM_VELTS returns a 'naked' pointer to
the SCM array of the the vector and the conservative scanning knows
nothing about this (it only knows about SCMs).
However, just assuming that the vector holds inums is not OK, I'd say.
You need to use scm_num2ulong and then check that it fits in a gid_t.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-04-18 10:31 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 ` Marius Vollmer [this message]
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 ` setgroups Paul Jarc
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=874r4w85b6.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
/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).