From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Cc: guile-devel@gnu.org
Subject: Re: mmap for guile
Date: Tue, 19 Jul 2022 15:34:54 +0200 [thread overview]
Message-ID: <e72ee087b351d5196e4fbcc7514fa23270b029e0.camel@telenet.be> (raw)
In-Reply-To: <87k08tfau0.fsf@gnu.org>
Ludovic Courtès schreef op ma 04-07-2022 om 12:09 [+0200]:
> > Also, what if you mmap a region, use bytevector->pointer and pass
> > it to
> > some C thing, which saves the pointer somewhere where boehm-gc can
> > find
> > it and boehm-gc considers it to be live, is there something that
> > prevents boehm-gc from improperly calling the finalizer & unmapping
> > the
> > region, causing a dangling pointer?
>
> There’s a risk, but I don’t think it’s specific to mmap.
AFAIK, make-bytevector doesn't have an issue here, so by default I
would assume mmap to not have it either, unless documented otherwise.
However, I am not seeing tests or analysis that verify there's no issue
here even though plausibly there might be an issue and neither am I
seeing documentation that this doesn't work (for mmap in specific, or
more generally).
Greetings,
Maxime.
next prev parent reply other threads:[~2022-07-19 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:37 mmap for guile Matt Wette
2022-06-26 16:21 ` Matt Wette
2022-06-26 17:06 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-06-26 18:11 ` Maxime Devos
2022-07-04 10:09 ` Ludovic Courtès
2022-07-04 12:59 ` Matt Wette
2022-07-04 13:14 ` Greg Troxel
2022-07-04 20:03 ` Ludovic Courtès
2022-07-19 13:20 ` Maxime Devos
2022-07-21 9:14 ` Ludovic Courtès
2022-07-19 13:30 ` Maxime Devos
2022-07-19 13:34 ` Maxime Devos [this message]
2022-06-26 18:21 ` Maxime Devos
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=e72ee087b351d5196e4fbcc7514fa23270b029e0.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).