From: Greg.mpls@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92687] [Ruby trunk Bug#15809] GC.verify_compaction_references - intermittent SEGV's on multiple platforms
Date: Thu, 16 May 2019 20:03:56 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-78046.20190516200355.1b03acde99217c7c@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15809.20190428164840@ruby-lang.org
Issue #15809 has been updated by MSP-Greg (Greg L).
@wanabe
Thank you for your work on this. Today, I had the SEGV fault again during a ruby-loco build, and have found that running the two following test files will cause a SEGV:
```
drb/test_drbobject.rb ruby/test_gc_compact.rb
```
I don't know if interaction with tests other than `drb/test_drbobject.rb` will cause a SEGV in `ruby/test_gc_compact.rb`.
`ruby/test_gc_compact.rb` seems to have been isolated in the CI here. Up to now, ruby-loco has reliably passed test-all running parallel with retry.
I don't know c, and even if I did, I wouldn't want to jump into GC code. Hence, I can't help with the issue.
It certainly seems incorrect to 'sweep the issue under the rug' via test isolation. I can't think of any code in Ruby that should include a caveat something like "this may SEGV if you use it with an indeterminate set of classes/modules/methods...
I may isolate the drb test in ruby-loco and see what happens...
----------------------------------------
Bug #15809: GC.verify_compaction_references - intermittent SEGV's on multiple platforms
https://bugs.ruby-lang.org/issues/15809#change-78046
* Author: MSP-Greg (Greg L)
* Status: Assigned
* Priority: Normal
* Assignee: tenderlovemaking (Aaron Patterson)
* Target version:
* ruby -v: ruby 2.7.0dev (2019-05-06 trunk c3cf1ef9bb) [x64-mingw32
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
See
https://travis-ci.org/ruby/ruby/jobs/525627187#L2684
https://ci.appveyor.com/project/ruby/ruby/builds/24138134/job/i7e441u7se11w7ey#L3402
Both have an error similar to:
```
/ruby/test/ruby/test_gc_compact.rb:128: [BUG] ROOT finalizers points to MOVED:
0x0000000004679c20 -> 0x00000000089367c0 [0 ] T_ARRAY [E ] len: 1 (embed)
```
ruby-loco has also failed with a similar error. Attached STDERR output.
---Files--------------------------------
test_all_err.log (42 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-05-16 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15809.20190428164840@ruby-lang.org>
2019-04-28 16:48 ` [ruby-core:92465] [Ruby trunk Bug#15809] GC.verify_compaction_references - intermittent SEGV's on multiple platforms Greg.mpls
2019-04-28 16:56 ` [ruby-core:92466] " takashikkbn
2019-05-06 16:53 ` [ruby-core:92576] " Greg.mpls
2019-05-07 13:42 ` [ruby-core:92584] " s.wanabe
2019-05-09 11:46 ` [ruby-core:92615] " s.wanabe
2019-05-10 0:41 ` [ruby-core:92618] " s.wanabe
2019-05-15 18:26 ` [ruby-core:92665] " Greg.mpls
2019-05-15 23:41 ` [ruby-core:92674] " s.wanabe
2019-05-16 20:03 ` Greg.mpls [this message]
2019-05-16 21:54 ` [ruby-core:92689] " Greg.mpls
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.journal-78046.20190516200355.1b03acde99217c7c@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).