From: usa@garbagecollect.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:69933] [Backport200 - Backport #9649] Segfault running thread_safe torture tests under Ruby 2.0
Date: Fri, 10 Jul 2015 08:55:31 +0000 [thread overview]
Message-ID: <redmine.journal-53355.20150710085530.b6a7d25e3bb26853@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-9649.20140317125458@ruby-lang.org
Issue #9649 has been updated by Usaku NAKAMURA.
The normal maintenance phase of ruby 2.0.0 is already ended.
Try ruby 2.1 or 2.2.
----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-53355
* Author: Charles Nutter
* Status: Closed
* Priority: Normal
* Assignee:
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32
It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.
I have not received any reports of segfaults other than this one.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2015-07-10 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
2014-03-17 12:54 ` [ruby-core:61553] [Backport200 - Backport #9649] [Open] Segfault running thread_safe torture tests under Ruby 2.0 headius
2014-03-17 20:57 ` [ruby-core:61566] " Eric Wong
2014-03-17 21:03 ` [ruby-core:61567] [Backport200 - Backport #9649] " normalperson
2014-04-30 6:05 ` [ruby-core:62236] [Backport200 - Backport #9649] [Closed] " usa
2015-07-10 8:36 ` [ruby-core:69930] [Backport200 - Backport #9649] " hans
2015-07-10 8:55 ` usa [this message]
2015-07-27 19:34 ` [ruby-core:70134] " hans
2015-07-27 19:57 ` [ruby-core:70136] " hans
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-53355.20150710085530.b6a7d25e3bb26853@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).