From: nagachika00@gmail•com
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:50409] [Ruby trunk Bug#14269] backport r61562, r61563, r61566 (fix SEGV touching uninitialized memory)
Date: Tue, 02 Jan 2018 14:31:10 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-69133.20180102143108.295cf987551cb86a@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-14269.20180102125132@ruby-lang.org
Issue #14269 has been updated by nagachika (Tomoyuki Chikanaga).
r61566 については ruby_2_3 では switch 文に default 節があるため未初期化のままアクセスされることはなく SEGV は発生しないと思いますが、初期化しておいて悪いことはないと思い REQUIRED のチケットに含めました。しかし backport は不要かもしれませんので最終判断は usa さんにお任せします。
----------------------------------------
Bug #14269: backport r61562, r61563, r61566 (fix SEGV touching uninitialized memory)
https://bugs.ruby-lang.org/issues/14269#change-69133
* Author: nagachika (Tomoyuki Chikanaga)
* Status: Closed
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: -
* Backport: 2.3: REQUIRED, 2.4: REQUIRED, 2.5: REQUIRED
----------------------------------------
backport 管理用チケットです。
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2018-01-02 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-14269.20180102125132@ruby-lang.org>
2018-01-02 12:51 ` [ruby-dev:50406] [Ruby trunk Bug#14269] backport r61562 (fix SEGV touching uninitialized memory) nagachika00
2018-01-02 14:31 ` nagachika00 [this message]
2018-01-24 8:11 ` [ruby-dev:50423] [Ruby trunk Bug#14269] backport r61562, r61563, r61566, r61568, r61569 " naruse
2018-03-19 18:16 ` [ruby-dev:50507] " nagachika00
2018-03-28 5:17 ` [ruby-dev:50514] " 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.journal-69133.20180102143108.295cf987551cb86a@ruby-lang.org \
--to=ruby-dev@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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).