ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: sam.saffron@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95449] [Ruby master Bug#16268] Consistent segfault with ObjectSpace.count_imemo_objects
Date: Mon, 21 Oct 2019 05:14:33 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-16268.20191021051433.9f2f44f98947c8cd@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16268.20191021051433@ruby-lang.org

Issue #16268 has been reported by sam.saffron (Sam Saffron).

----------------------------------------
Bug #16268: Consistent segfault with ObjectSpace.count_imemo_objects
https://bugs.ruby-lang.org/issues/16268

* Author: sam.saffron (Sam Saffron)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.6.5
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
On 2.6.5: 

> irb
> require 'objspace'
> ObjectSpace.count_imemo_objects

Segfaults with:

```
/usr/local/lib/ruby/2.6.0/irb/inspector.rb:109: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]

-- Control frame information -----------------------------------------------
c:0023 p:---- s:0100 e:000099 CFUNC  :inspect
c:0022 p:---- s:0097 e:000096 CFUNC  :inspect
c:0021 p:0006 s:0093 e:000092 BLOCK  /usr/local/lib/ruby/2.6.0/irb/inspector.rb:109
c:0020 p:0008 s:0089 e:000088 METHOD /usr/local/lib/ruby/2.6.0/irb/inspector.rb:102
c:0019 p:0009 s:0084 e:000083 METHOD /usr/local/lib/ruby/2.6.0/irb/context.rb:389
c:0018 p:0013 s:0080 e:000077 METHOD /usr/local/lib/ruby/2.6.0/irb.rb:685
c:0017 p:0033 s:0074 e:000073 BLOCK  /usr/local/lib/ruby/2.6.0/irb.rb:494
c:0016 p:0025 s:0071 e:000070 METHOD /usr/local/lib/ruby/2.6.0/irb.rb:647
c:0015 p:0008 s:0065 e:000064 BLOCK  /usr/local/lib/ruby/2.6.0/irb.rb:490
c:0014 p:0100 s:0060 e:000059 BLOCK  /usr/local/lib/ruby/2.6.0/irb/ruby-lex.rb:246 [FINISH]
c:0013 p:---- s:0056 e:000055 CFUNC  :loop
c:0012 p:0006 s:0052 e:000051 BLOCK  /usr/local/lib/ruby/2.6.0/irb/ruby-lex.rb:232 [FINISH]
c:0011 p:---- s:0049 e:000048 CFUNC  :catch
c:0010 p:0012 s:0044 e:000043 METHOD /usr/local/lib/ruby/2.6.0/irb/ruby-lex.rb:231
c:0009 p:0034 s:0040 E:0024a8 METHOD /usr/local/lib/ruby/2.6.0/irb.rb:489
c:0008 p:0005 s:0035 e:000034 BLOCK  /usr/local/lib/ruby/2.6.0/irb.rb:428 [FINISH]
c:0007 p:---- s:0032 e:000031 CFUNC  :catch
c:0006 p:0064 s:0027 E:002448 METHOD /usr/local/lib/ruby/2.6.0/irb.rb:427
c:0005 p:0102 s:0022 e:000021 METHOD /usr/local/lib/ruby/2.6.0/irb.rb:383
c:0004 p:0019 s:0016 e:000015 TOP    /usr/local/lib/ruby/gems/2.6.0/gems/irb-1.0.0/exe/irb:11 [FINISH]
c:0003 p:---- s:0013 e:000012 CFUNC  :load
c:0002 p:0109 s:0008 E:001200 EVAL   /usr/local/bin/irb:23 [FINISH]
c:0001 p:0000 s:0003 E:0013f0 (none) [FINISH]


```

Works fine in Ruby master



-- 
https://bugs.ruby-lang.org/

       reply	other threads:[~2019-10-21  5:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-16268.20191021051433@ruby-lang.org>
2019-10-21  5:14 ` sam.saffron [this message]
2019-10-21  7:05 ` [ruby-core:95450] [Ruby master Bug#16268] Consistent segfault with ObjectSpace.count_imemo_objects ko1

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-16268.20191021051433.9f2f44f98947c8cd@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).