From: Andy Wingo <wingo@pobox.com>
To: Jan Schukat <shookie@email.de>
Cc: 13768-done@debbugs.gnu.org
Subject: bug#13768: --without-posix code uses scm_getpid() in libguile-2.0.2
Date: Sun, 24 Feb 2013 20:21:54 +0100 [thread overview]
Message-ID: <87ip5hcyb1.fsf@pobox.com> (raw)
In-Reply-To: <51240CE7.8030802@email.de> (Jan Schukat's message of "Wed, 20 Feb 2013 00:38:15 +0100")
On Wed 20 Feb 2013 00:38, Jan Schukat <shookie@email.de> writes:
> What happens is, in random.c in random_state_of_last_resort on line 668
> scm_getpid is used to seed the random generator. So either a
> preprocessor switch or a hand constructed scm like in scm_getpid
> (scm_from_ulong(getpid())) should be used there.
Fixed, thanks for the report.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-02-24 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 23:38 bug#13768: --without-posix code uses scm_getpid() in libguile-2.0.2 Jan Schukat
2013-02-24 19:21 ` Andy Wingo [this message]
2013-02-25 1:17 ` Mark H Weaver
2013-02-25 9:06 ` Andy Wingo
2013-02-25 18:58 ` Mark H Weaver
2013-02-25 20:39 ` Andy Wingo
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=87ip5hcyb1.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=13768-done@debbugs.gnu.org \
--cc=shookie@email.de \
/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).