Actions
Bug #11830
closedhash.each(&:destroy) dumps core
Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 2.3.0dev (2015-12-17 trunk 53168) [x86_64-linux]
Description
Following small code dumps core.
$ ./ruby --disable-gems -e '{}.each(&:destroy)'
-e:1: [BUG] Segmentation fault at 0x00000000aaf12c
ruby 2.3.0dev (2015-12-17 trunk 53168) [x86_64-linux]
... see attached crash report ...
Aborted (core dumped)
Array and Range works fine.
$ ./ruby -e '[1].each(&:destroy)'
-e:1:in `each': undefined method `destroy' for 1:Fixnum (NoMethodError)
from -e:1:in `<main>'
$ ./ruby -e '(1..2).each(&:destroy)'
-e:1:in `each': undefined method `destroy' for 1:Fixnum (NoMethodError)
from -e:1:in `<main>'
In rb_block_arity(), block->proc and block->iseq are invalid value I think.
$ gdb /home/tietew/ruby/ruby2.3-trunk/bin/ruby core
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
...
Program terminated with signal SIGABRT, Aborted.
(gdb) bt
...
#5 <signal handler called>
#6 rb_block_arity () at proc.c:960
...
(gdb) frame 6
#6 rb_block_arity () at proc.c:960
960 GetProcPtr(proc_value, proc);
(gdb) p proc_value
$1 = 7643404
(gdb) p proc
$2 = <optimized out>
(gdb) p *(struct RBasic *)proc_value
Cannot access memory at address 0x74a10c
(gdb) p *block
$5 = {self = 139733405230640, ep = 0x7f16380bd9d0, iseq = 0x74a10c,
proc = 7643404}
(gdb)
Files
Updated by Tietew (Toru Iwase) over 8 years ago
Ruby 2.2 and earlier are OK.
$ RBENV_VERSION=2.2.4 ruby -ve '{1=>1}.each(&:destroy)'
ruby 2.2.4p230 (2015-12-16 revision 53155) [x86_64-linux]
-e:1:in `each': undefined method `destroy' for [1, 1]:Array (NoMethodError)
from -e:1:in `<main>'
$ RBENV_VERSION=2.1.8 ruby -ve '{1=>1}.each(&:destroy)'
ruby 2.1.8p440 (2015-12-16 revision 53160) [x86_64-linux]
-e:1:in `each': undefined method `destroy' for [1, 1]:Array (NoMethodError)
from -e:1:in `<main>'
$ RBENV_VERSION=2.0.0-p648 ruby -ve '{1=>1}.each(&:destroy)'
ruby 2.0.0p648 (2015-12-16 revision 53162) [x86_64-linux]
-e:1:in `each': undefined method `destroy' for [1, 1]:Array (NoMethodError)
from -e:1:in `<main>'
Updated by Hanmac (Hans Mackowiak) over 8 years ago
i think it has something to do with this fix:
https://bugs.ruby-lang.org/issues/11811
maybe the bug is caused by this.
Updated by shugo (Shugo Maeda) over 8 years ago
- Status changed from Open to Closed
Applied in changeset r53170.
- proc.c (rb_block_arity): should not call GetProcPtr() for symbols.
[ruby-core:72205] [Bug #11830]
Updated by nagachika (Tomoyuki Chikanaga) over 8 years ago
- Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN to 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONTNEED
Updated by nobu (Nobuyoshi Nakada) over 8 years ago
- Has duplicate Bug #11861: `zip` with `&symbol` causes segmentation error added
Actions
Like0
Like0Like0Like0Like0Like0