From: usa@garbagecollect.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:65720] [ruby-trunk - Bug #10373] add RB_GC_GUARD in rb_mod_define_method() (r47891)
Date: Wed, 15 Oct 2014 07:16:56 +0000 [thread overview]
Message-ID: <redmine.journal-49452.20141015071656.8c2d47da5ccb93d7@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-10373.20141012134652@ruby-lang.org
Issue #10373 has been updated by Usaku NAKAMURA.
Backport changed from 2.0.0: REQUIRED, 2.1: REQUIRED to 2.0.0: DONE, 2.1: REQUIRED
Backported into `ruby_2_0_0` at r47935.
----------------------------------------
Bug #10373: add RB_GC_GUARD in rb_mod_define_method() (r47891)
https://bugs.ruby-lang.org/issues/10373#change-49452
* Author: Tomoyuki Chikanaga
* Status: Closed
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* Category: core
* Target version: current: 2.2.0
* ruby -v: -
* Backport: 2.0.0: DONE, 2.1: REQUIRED
----------------------------------------
This ticket is for backport management.
r47891 added RB_GC_GUARD() in rb_mod_define_method() to protect method entry (VALUE body which can be derived from rb_block_lambda()) from unexpected GC.
It seemsd `ruby_2_1` and `ruby_2_0_0` have similar potential problem.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2014-10-15 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-10373.20141012134652@ruby-lang.org>
2014-10-12 13:46 ` [ruby-core:65632] [ruby-trunk - Bug #10373] [Closed] add RB_GC_GUARD in rb_mod_define_method() (r47891) nagachika00
2014-10-15 7:16 ` usa [this message]
2014-10-15 14:12 ` [ruby-core:65727] [ruby-trunk - Bug #10373] " nagachika00
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=redmine.journal-49452.20141015071656.8c2d47da5ccb93d7@ruby-lang.org \
--to=ruby-core@ruby-lang.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).