ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: eagletmt@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:69692] [Ruby trunk - Bug #11291] [Open] [PATCH] Check SPECIAL_CONST_P before RBASIC_CLASS to avoid SEGV
Date: Sat, 20 Jun 2015 17:06:55 +0000	[thread overview]
Message-ID: <redmine.issue-11291.20150620170654.98268fd6eddf2c2e@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11291.20150620170654@ruby-lang.org

Issue #11291 has been reported by Kohei Suzuki.

----------------------------------------
Bug #11291: [PATCH] Check SPECIAL_CONST_P before RBASIC_CLASS to avoid SEGV
https://bugs.ruby-lang.org/issues/11291

* Author: Kohei Suzuki
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
https://github.com/ruby/ruby/pull/943

It fixes SEGV when a special constant is passed to `ObjectSpace.dump` .
I think it needs to be backported to 2.1 and 2.2.



-- 
https://bugs.ruby-lang.org/

       reply	other threads:[~2015-06-20 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11291.20150620170654@ruby-lang.org>
2015-06-20 17:06 ` eagletmt [this message]
2015-06-20 20:46 ` [ruby-core:69693] [Ruby trunk - Bug #11291] [PATCH] Check SPECIAL_CONST_P before RBASIC_CLASS to avoid SEGV her
2015-06-27 14:13 ` [ruby-core:69757] " nagachika00
2015-06-29  4:28 ` [ruby-core:69766] " usa

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.issue-11291.20150620170654.98268fd6eddf2c2e@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).