From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Cc: unicorn-public@yhbt.net
Subject: [ruby-core:99185] Re: [Ruby master Bug#17023] How to prevent String memory to be relocated in ruby-ffi
Date: Wed, 15 Jul 2020 23:35:40 +0000 [thread overview]
Message-ID: <20200715233540.GA14457@dcvr> (raw)
In-Reply-To: <redmine.journal-86563.20200715200039.5550@ruby-lang.org>
tenderlove@ruby-lang.org wrote:
> Right, that makes sense. I really need to document this (and
> I apologize for not doing so already), but
> `rb_gc_register_address` will pin your objects. When you know
> you're done with the reference, you can release it with
> `rb_gc_unregister_address`. Of course if you don't call the
> unregister function, the reference will stay alive forever.
Btw, does rb_gc_register_mark_object pin? A quick glance at
gc.c tells me it doesn't, and I'll need to revert commit
2a6cb76d5010cb763ef5a2c305728465d15eb7c9 in unicorn:
https://yhbt.net/unicorn-public/20181226050857.6413-1-e@80x24.org/
Anyways, it takes me too long to compile Ruby so I'm back to
running whatever my distro ships. I haven't been able to
test GC.compact at all.
> https://bugs.ruby-lang.org/issues/17023#change-86563
next prev parent reply other threads:[~2020-07-15 23:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 17:54 [ruby-core:99115] [Ruby master Bug#17023] How to prevent String memory to be relocated in ruby-ffi larskanis
2020-07-10 19:51 ` [ruby-core:99116] " chris
2020-07-10 21:11 ` [ruby-core:99118] " larskanis
2020-07-11 0:24 ` [ruby-core:99120] " duerst
2020-07-11 10:11 ` [ruby-core:99126] " nobu
2020-07-12 16:51 ` [ruby-core:99140] " tenderlove
2020-07-13 17:55 ` [ruby-core:99155] " tenderlove
2020-07-15 19:35 ` [ruby-core:99183] " larskanis
2020-07-15 20:00 ` [ruby-core:99184] " tenderlove
2020-07-15 23:35 ` Eric Wong [this message]
[not found] ` <647A6735-04C8-4410-A71A-307A2390CFBD@gmail.com>
2020-07-16 0:04 ` [ruby-core:99186] " Eric Wong
2020-07-19 2:52 ` [ruby-core:99218] " nagachika00
2020-07-21 20:18 ` [ruby-core:99254] " larskanis
2020-07-22 7:41 ` [ruby-core:99260] " hanmac
2020-07-22 9:46 ` [ruby-core:99262] " larskanis
2020-07-22 17:57 ` [ruby-core:99273] " tenderlove
2020-07-22 18:19 ` [ruby-core:99275] " eregontp
2020-07-22 18:23 ` [ruby-core:99276] " tenderlove
2020-07-22 19:47 ` [ruby-core:99280] " eregontp
2020-08-02 20:34 ` [ruby-core:99446] " larskanis
2020-08-18 18:14 ` [ruby-core:99630] " larskanis
2020-08-18 18:57 ` [ruby-core:99631] " tenderlove
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200715233540.GA14457@dcvr \
--to=ruby-core@ruby-lang.org \
--cc=unicorn-public@yhbt.net \
/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).