Bug #9440
closed
Calling methods on a `Queue.new.dup` or `Queue.new.clone` causes Segfault
Added by shan (Shannon Skipper) almost 11 years ago.
Updated almost 10 years ago.
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.
- 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]
- Backport changed from 2.1: UNKNOWN to 2.1: REQUIRED
- Related to Bug #10485: NoMethodError "undefined method `initialize_copy'" when trying to execute Queue#dup added
- Backport changed from 2.1: REQUIRED to 2.1: DONE
Backported into ruby_2_1
at r50044.
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0