Forum: Ruby-core [Closed] Segfault involving Queue

F1d6cc2b735bfd82c8773172da2aeab9?d=identicon&s=25 Nobuyoshi Nakada (nobu)
on 2014-08-19 03:14
(Received via mailing list)
Issue #10062 has been updated by Nobuyoshi Nakada.

Status changed from Feedback to Closed
% Done changed from 0 to 100

Applied in changeset r47217.

----------
thread.c: check initialized

* ext/thread/thread.c (get_array): check instance variables are
  initialized properly.  [ruby-core:63826][Bug #10062]

----------------------------------------
Bug #10062: Segfault involving Queue
https://bugs.ruby-lang.org/issues/10062#change-48402

* Author: Fred Mitchell
* Status: Closed
* Priority: Normal
* Assignee:
* Category:
* Target version:
* ruby -v: trun
* Backport: 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
Pushing an object onto a `Queue` instantiation causes a segfault. This
was seen on Ruby versions 2.1.1 and 2.1.2

In the interests of being able to completely reproduce the environment
in which this happens, I have included detailed instructions here.

1. Clone https://github.com/flajann2/rubyneat/tree/devready (yes, the
devready branch)
2. In its root do "rake install" to install the gem
3. Clone https://github.com/flajann2/rubyneat_dashboard/tree/master
4. In its root do "rake install" to install that gem
5. Clone https://github.com/flajann2/rubyneat_examples/tree/devready
(yes, the devready branch)
6. Go to the root of that and
7. Run "bundle update"
8. Run "neat run xor"
9. It should segfault almost immediately.


---Files--------------------------------
bug-10062.txt (189 KB)
This topic is locked and can not be replied to.