* [ruby-core:75724] [Ruby trunk Bug#12430] Segfault in irb when improperly using coerce in combination with method_missing
[not found] <redmine.issue-12430.20160525211417@ruby-lang.org>
@ 2016-05-25 21:14 ` gregory.t.brown
2016-05-25 21:23 ` [ruby-core:75725] " gregory.t.brown
2019-07-24 23:30 ` [ruby-core:93906] [Ruby master " merch-redmine
2 siblings, 0 replies; 3+ messages in thread
From: gregory.t.brown @ 2016-05-25 21:14 UTC (permalink / raw
To: ruby-core
Issue #12430 has been reported by Gregory Brown.
----------------------------------------
Bug #12430: Segfault in irb when improperly using coerce in combination with method_missing
https://bugs.ruby-lang.org/issues/12430
* Author: Gregory Brown
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v:
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
Don't ask how or why I wrote this code, but suppose you have a class like this:
~~~
class BrokenNumber
def initialize(num)
@num = num
end
def method_missing(m, *a, &b)
@num.send(m, *a, &b)
end
def coerce(other)
[self, self]
end
end
~~~
Then you require this code in IRB, and you create a new instance (x) and you then call 2+x.
The first call will raise a SystemStackError. The second will cause a segmentation fault.
~~~
>> require "./broken"
=> true
>> x = BrokenNumber.new(2)
=> #<BrokenNumber:0x007f8b5a84c190 @num=2>
>> 2 + x
SystemStackError: stack level too deep
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
... 7559 levels...
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from (irb):3:in `+'
from (irb):3
from /Users/gtb/.rubies/ruby-2.3.1/bin/irb:11:in `<main>'
>> 2 + x
Segmentation fault: 11
MacBook-Pro:~ gtb$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
~~~
I've asked multiple people to confirm this and they've reproduced the error. I have no clue how to debug it, but thought it may be worth mentioning... even though it's a strange corner case and invalid code.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:75725] [Ruby trunk Bug#12430] Segfault in irb when improperly using coerce in combination with method_missing
[not found] <redmine.issue-12430.20160525211417@ruby-lang.org>
2016-05-25 21:14 ` [ruby-core:75724] [Ruby trunk Bug#12430] Segfault in irb when improperly using coerce in combination with method_missing gregory.t.brown
@ 2016-05-25 21:23 ` gregory.t.brown
2019-07-24 23:30 ` [ruby-core:93906] [Ruby master " merch-redmine
2 siblings, 0 replies; 3+ messages in thread
From: gregory.t.brown @ 2016-05-25 21:23 UTC (permalink / raw
To: ruby-core
Issue #12430 has been updated by Gregory Brown.
ruby -v set to ruby 2.3.1p112
----------------------------------------
Bug #12430: Segfault in irb when improperly using coerce in combination with method_missing
https://bugs.ruby-lang.org/issues/12430#change-58852
* Author: Gregory Brown
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.3.1p112
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
Don't ask how or why I wrote this code, but suppose you have a class like this:
~~~
class BrokenNumber
def initialize(num)
@num = num
end
def method_missing(m, *a, &b)
@num.send(m, *a, &b)
end
def coerce(other)
[self, self]
end
end
~~~
Then you require this code in IRB, and you create a new instance (x) and you then call 2+x.
The first call will raise a SystemStackError. The second will cause a segmentation fault.
~~~
>> require "./broken"
=> true
>> x = BrokenNumber.new(2)
=> #<BrokenNumber:0x007f8b5a84c190 @num=2>
>> 2 + x
SystemStackError: stack level too deep
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
... 7559 levels...
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from (irb):3:in `+'
from (irb):3
from /Users/gtb/.rubies/ruby-2.3.1/bin/irb:11:in `<main>'
>> 2 + x
Segmentation fault: 11
MacBook-Pro:~ gtb$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
~~~
I've asked multiple people to confirm this and they've reproduced the error. I have no clue how to debug it, but thought it may be worth mentioning... even though it's a strange corner case and invalid code.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:93906] [Ruby master Bug#12430] Segfault in irb when improperly using coerce in combination with method_missing
[not found] <redmine.issue-12430.20160525211417@ruby-lang.org>
2016-05-25 21:14 ` [ruby-core:75724] [Ruby trunk Bug#12430] Segfault in irb when improperly using coerce in combination with method_missing gregory.t.brown
2016-05-25 21:23 ` [ruby-core:75725] " gregory.t.brown
@ 2019-07-24 23:30 ` merch-redmine
2 siblings, 0 replies; 3+ messages in thread
From: merch-redmine @ 2019-07-24 23:30 UTC (permalink / raw
To: ruby-core
Issue #12430 has been updated by jeremyevans0 (Jeremy Evans).
Status changed from Open to Closed
I don't think this is a bug, the SystemStackError is expected. In some cases, Ruby doesn't catch the stack overflow and you end up with a segfault.
The reason for the behavior:
```ruby
x = BrokenNumber.new(2)
# original expression
2 + x
# Integer#+ calls (via rb_num_coerce_bin->do_coerce):
x.coerce(2)
# x.coerce(2) returns:
[x, x]
# Integer#+ calls (via rb_num_coerce_bin):
x + x
# BrokenNumber#+ not defined, so calls:
x.method_missing(:+, x)
# BrokenNumber#method_missing calls:
2 + x # the original expression, so a loop
```
----------------------------------------
Bug #12430: Segfault in irb when improperly using coerce in combination with method_missing
https://bugs.ruby-lang.org/issues/12430#change-79996
* Author: sandal (Gregory Brown)
* Status: Closed
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.3.1p112
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
Don't ask how or why I wrote this code, but suppose you have a class like this:
~~~
class BrokenNumber
def initialize(num)
@num = num
end
def method_missing(m, *a, &b)
@num.send(m, *a, &b)
end
def coerce(other)
[self, self]
end
end
~~~
Then you require this code in IRB, and you create a new instance (x) and you then call 2+x.
The first call will raise a SystemStackError. The second will cause a segmentation fault.
~~~
>> require "./broken"
=> true
>> x = BrokenNumber.new(2)
=> #<BrokenNumber:0x007f8b5a84c190 @num=2>
>> 2 + x
SystemStackError: stack level too deep
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
... 7559 levels...
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from /Users/gtb/broken.rb:7:in `+'
from /Users/gtb/broken.rb:7:in `method_missing'
from (irb):3:in `+'
from (irb):3
from /Users/gtb/.rubies/ruby-2.3.1/bin/irb:11:in `<main>'
>> 2 + x
Segmentation fault: 11
MacBook-Pro:~ gtb$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
~~~
I've asked multiple people to confirm this and they've reproduced the error. I have no clue how to debug it, but thought it may be worth mentioning... even though it's a strange corner case and invalid code.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-07-24 23:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <redmine.issue-12430.20160525211417@ruby-lang.org>
2016-05-25 21:14 ` [ruby-core:75724] [Ruby trunk Bug#12430] Segfault in irb when improperly using coerce in combination with method_missing gregory.t.brown
2016-05-25 21:23 ` [ruby-core:75725] " gregory.t.brown
2019-07-24 23:30 ` [ruby-core:93906] [Ruby master " merch-redmine
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).