Project

General

Profile

Actions
Copy link

Bug #9440

closed

Calling methods on a `Queue.new.dup` or `Queue.new.clone` causes Segfault

Bug #9440: Calling methods on a `Queue.new.dup` or `Queue.new.clone` causes Segfault

Added by shan (Shannon Skipper) over 12 years ago. Updated over 11 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
2.1.0p0
Backport:
2.1: DONE
[ruby-core:59961]

Description

On all platforms with ruby-2.1.0 calling a Queue#method on a duped or cloned Queue results in a Segfault:

queue = Queue.new.dup
queue.empty? # Segfault

The same issue occurs when calling other Queue#methods.

Related issues 1 (0 open — 1 closed)

Related to Ruby - Bug #10485: NoMethodError "undefined method `initialize_copy'" when trying to execute Queue#dupClosedActions

Updated by nobu (Nobuyoshi Nakada) over 12 years ago Actions
Copy link
 #1 [ruby-core:59965]

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Applied in changeset r44681.

thread/thread.c: no dup

  • ext/thread/thread.c (Init_thread): ConditionVariable and Queue
    are not able to copy. [ruby-core:59961] [Bug #9440]

Updated by nobu (Nobuyoshi Nakada) over 11 years ago Actions
Copy link
 #2 [ruby-core:66129]

  • Backport changed from 2.1: UNKNOWN to 2.1: REQUIRED

Updated by nobu (Nobuyoshi Nakada) over 11 years ago Actions
Copy link
 #3 [ruby-core:66130]

  • Related to Bug #10485: NoMethodError "undefined method `initialize_copy'" when trying to execute Queue#dup added

Updated by nagachika (Tomoyuki Chikanaga) over 11 years ago Actions
Copy link
 #4

  • Backport changed from 2.1: REQUIRED to 2.1: DONE

Backported into ruby_2_1 at r50044.

Actions
Copy link

Also available in: PDF Atom