From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Mon, 27 Feb 2017 21:30:09 +0100 [thread overview]
Message-ID: <878torqsvi.fsf@pobox.com> (raw)
In-Reply-To: <997347203.1912023.1488223974132@mail.yahoo.com> (Mike Gran's message of "Mon, 27 Feb 2017 19:32:54 +0000 (UTC)")
On Mon 27 Feb 2017 20:32, Mike Gran <spk121@yahoo.com> writes:
> A C++ STL container holds a set of STL-allocated (non-GC allocated)
> structs.
>
> Those STL-allocated structs are also used as the payloads of
> SCM foreign objects.
>
> STL destruction can free those objects. That free
> should not allow SCM foreign objects that continue to exist but
> contain junk payloads.
>
> Also should SCM GC free the SCM foreign objects, this GC
> should not cause the non-GC-allocated payload to be freed.
I believe this issue was fixed in
8dff3af087c6eaa83ae0d72aa8b22aef5c65d65d in Guile 2.0 and in a related
commit in 2.2.
Andy
next prev parent reply other threads:[~2017-02-27 20:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 10:31 GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-18 14:34 ` GNU Guile 2.1.7 released (beta), SOCK_NONBLOCK Matt Wette
2017-02-21 20:58 ` Andy Wingo
2017-02-18 17:40 ` GNU Guile 2.1.7 released (beta) Matt Wette
2017-02-18 17:48 ` Matt Wette
2017-02-23 18:54 ` Andy Wingo
2017-02-23 20:04 ` Mike Gran
2017-02-23 21:06 ` Andy Wingo
2017-02-24 0:52 ` Break-when [was GNU Guile 2.1.7 released (beta)] Matt Wette
2017-02-24 14:02 ` GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-24 17:46 ` Arne Babenhauserheide
2017-02-26 17:57 ` Andy Wingo
2017-02-27 19:32 ` Mike Gran
2017-02-27 20:30 ` Andy Wingo [this message]
2017-02-27 23:00 ` Thomas Morley
2017-02-28 8:31 ` Andy Wingo
2017-03-05 16:54 ` Thomas Morley
2017-03-01 18:04 ` Arne Babenhauserheide
2017-02-28 0:04 ` David Pirotte
2017-02-28 1:49 ` Daniel Llorens
2017-03-02 20:54 ` David Pirotte
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=878torqsvi.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=spk121@yahoo.com \
/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).