From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 20209-done@debbugs.gnu.org
Subject: bug#20209: GUILE 2.0.11: crash in set_port_filename_x for bytevector ports
Date: Tue, 28 Feb 2017 14:20:14 +0100 [thread overview]
Message-ID: <87innuo3jl.fsf@pobox.com> (raw)
In-Reply-To: <87r3bnn9tq.fsf@pobox.com> (Andy Wingo's message of "Thu, 23 Jun 2016 18:34:09 +0200")
On Thu 23 Jun 2016 18:34, Andy Wingo <wingo@pobox.com> writes:
> From: Andy Wingo <wingo@pobox.com>
> Date: Thu, 23 Jun 2016 18:31:55 +0200
> Subject: [PATCH] Register R6RS port and bytevector internals early
>
> * libguile/bytevectors.c (sym_big, sym_little): Rename from scm_sym_big
> and scm_sym_little, and don't use the snarf mechanism as we need to
> initialize this value eagerly in case the C API is used before the
> Scheme module is loaded.
> (scm_bootstrap_bytevectors): Initialize the endianness symbols here.
> * libguile/r6rs-ports.c (scm_register_r6rs_ports): Register the R6RS
> port kinds here, for the same reason.
Already applied to 2.0; now applied to master too.
Andy
prev parent reply other threads:[~2017-02-28 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 20:18 bug#20209: GUILE 2.0.11: crash in set_port_filename_x for bytevector ports David Kastrup
2015-03-26 23:02 ` Mark H Weaver
2015-03-27 8:18 ` David Kastrup
2015-03-28 18:48 ` Mark H Weaver
2015-03-28 18:21 ` Mark H Weaver
2015-03-29 13:06 ` Ludovic Courtès
2016-06-23 16:34 ` Andy Wingo
2016-06-23 16:59 ` David Kastrup
2016-06-23 18:01 ` Andy Wingo
2016-06-23 18:45 ` David Kastrup
2017-02-28 13:20 ` Andy Wingo [this message]
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=87innuo3jl.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=20209-done@debbugs.gnu.org \
--cc=ludo@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).