Bug #13841: Segmentation fault in Ruby CFUNC :to_s

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.3.4p301 (2017-03-30 revision 58214) [x86_64-linux-gnu]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN

[douyleyuyu (yubin liu)]

Hi, a segmentation fault was found in my environment.

E, [2017-08-25T16:21:37.798828 #632] ERROR -- : reaped #<Process::Status: pid 30125 SIGABRT (signal 6) (core dumped)> worker=2
I, [2017-08-25T16:21:37.826008 #30226]  INFO -- : worker=2 ready
$PATH_TO_HOME/gitlab/vendor/bundle/ruby/2.3.0/gems/gon-6.1.0/lib/gon/base.rb:37: [BUG] Segmentation fault at 0x00000000000000
ruby 2.3.4p301 (2017-03-30 revision 58214) [x86_64-linux-gnu]

-- Control frame information -----------------------------------------------
c:0173 p:---- s:0948 e:000947 CFUNC  :to_s
c:0172 p:0009 s:0946 e:000944 BLOCK  $PATH_TO_HOME/gitlab/vendor/bundle/ruby/2.3.0/gems/gon-6.1.0/lib/gon/base.rb:37 [FINISH]
c:0171 p:---- s:0941 e:000940 CFUNC  :each
c:0170 p:0029 s:0938 e:000937 METHOD $PATH_TO_HOME/gitlab/vendor/bundle/ruby/2.3.0/gems/gon-6.1.0/lib/gon/base.rb:36

#####################################################
$PATH_TO_HOME/gitlab/vendor/bundle/ruby/2.3.0/gems/jwt-1.5.6/lib/jwt/verify.rb:99: [BUG] Segmentation fault at 0x00000000000000
ruby 2.3.4p301 (2017-03-30 revision 58214) [x86_64-linux-gnu]

-- Control frame information -----------------------------------------------
c:0119 p:---- s:0643 e:000642 CFUNC  :to_s

The detail log was in attachement file.

[douyleyuyu (yubin liu)]

• Description updated (diff)

[douyleyuyu (yubin liu)]

• Description updated (diff)

[sonots (Naotoshi Seo)]

Hi, we need a reproducible codes.

[thaynel2 (Thayne McCombs)]

I get this somewhat inconsistently when running chef-solo on ubuntu 16.04.

Ruby version ruby 2.3.5p376 (2017-09-14 revision 59905) [x86_64-linux-gnu]

It will happen for a while, but eventually it will stop happening. It seems to be non-deterministic.

The segfault happens on line 74 of /usr/lib/ruby/vendor_ruby/ohai/mash.rb which is:

if key.is_a?(Symbol) && include?(key = key.to_s)

So, it has something to do with calling to_s on a Symbol. Maybe it is a problem with interning symbols?

[jeremyevans0 (Jeremy Evans)]

• Status changed from Open to Closed