From: satishdewangan@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95154] [Ruby master Bug#16135] Segmentation fault in Ruby 2.6.1
Date: Mon, 30 Sep 2019 14:18:58 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-81794.20190930141857.29eefb200a7962e7@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16135.20190903055603@ruby-lang.org
Issue #16135 has been updated by satishdewangan (Satish Dwangan).
We have a Ruby swig interface through which we are calling Kysy dll (written in C++) .I have upgraded swig interface from Ruby 2.2.6 to Ruby 2.6.1 .The same testcases are fine in Ruby 2.2.6 .I even tried with Ruby 2.5.6 versions and it works .
----------------------------------------
Bug #16135: Segmentation fault in Ruby 2.6.1
https://bugs.ruby-lang.org/issues/16135#change-81794
* Author: satishdewangan (Satish Dwangan)
* Status: Third Party's Issue
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
I am facing Segmentation fault issue while running test cases for my application in Ruby 2.6.1 .Same test cases work fine in Ruby 2.2.6 .
Below is the output of test case ran using Ruby 2.6.1.
```
C:/Code/KYSY-3153/Source/test/unit/ruby/ppr_register_access_test.rb:286: [BUG] Segmentation fault
ruby 2.6.1p33 (2019-01-30 revision 66950) [x64-mingw32]
```
Please help me to fix this issue.
---Files--------------------------------
bug-16135.txt (32.8 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-09-30 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16135.20190903055603@ruby-lang.org>
2019-09-03 5:56 ` [ruby-core:94753] [Ruby master Bug#16135] Segmentation fault in Ruby 2.6.1 satishdewangan
2019-09-03 23:04 ` [ruby-core:94765] " merch-redmine
2019-09-20 16:21 ` [ruby-core:95004] " satishdewangan
2019-09-20 16:25 ` [ruby-core:95005] " satishdewangan
2019-09-20 16:29 ` [ruby-core:95006] " merch-redmine
2019-09-23 5:42 ` [ruby-core:95041] " satishdewangan
2019-09-23 9:09 ` [ruby-core:95042] " satishdewangan
2019-09-23 15:12 ` [ruby-core:95043] " merch-redmine
2019-09-24 6:27 ` [ruby-core:95054] " satishdewangan
2019-09-24 14:36 ` [ruby-core:95061] " merch-redmine
2019-09-25 5:10 ` [ruby-core:95076] " satishdewangan
2019-09-25 7:13 ` [ruby-core:95077] " nobu
2019-09-26 3:46 ` [ruby-core:95096] " satishdewangan
2019-09-30 14:18 ` satishdewangan [this message]
2019-10-10 14:39 ` [ruby-core:95297] " satishdewangan
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-81794.20190930141857.29eefb200a7962e7@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).