From: mame@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:88891] [Ruby trunk Bug#15087] Segmentation fault with splat and block
Date: Fri, 07 Sep 2018 15:07:16 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-73934.20180907150715.cb8f5e77b46be295@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15087.20180907145831@ruby-lang.org
Issue #15087 has been updated by mame (Yusuke Endoh).
Good catch. My patch for #15052 will fix this issue.
----------------------------------------
Bug #15087: Segmentation fault with splat and block
https://bugs.ruby-lang.org/issues/15087#change-73934
* Author: jacobevelyn (Jacob Evelyn)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: 2.5.0, 2.5.1, 2.6.0dev (2018-09-07 trunk 64656)
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
The following code produces segmentation faults in Ruby 2.5.0, 2.5.1, and 2.6.0dev (2018-09-07 trunk 64656). This code worked in Ruby 2.4.1.
~~~ ruby
test_proc = Proc.new { "test" }
def foo(bar: 1, &block)
yield
end
foo(**{}, &test_proc)
~~~
I've attached the crash reports for both Ruby 2.6.0dev (2018-09-07 trunk 64656) and 2.5.1. Let me know if there's anything else I can provide.
---Files--------------------------------
ruby_2.6.0dev-2018-09-07-105158_Jacobs-MacBook-Pro.crash (36.4 KB)
ruby_2.5.1-2018-09-07-105813_Jacobs-MacBook-Pro.crash (36.4 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2018-09-07 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15087.20180907145831@ruby-lang.org>
2018-09-07 14:58 ` [ruby-core:88890] [Ruby trunk Bug#15087] Segmentation fault with splat and block jacobevelyn
2018-09-07 15:07 ` mame [this message]
2018-09-20 1:23 ` [ruby-core:89087] " mame
2018-11-02 19:31 ` [ruby-core:89681] " msiegel
2018-11-03 5:35 ` [ruby-core:89691] " nobu
2018-11-06 14:50 ` [ruby-core:89725] " nagachika00
2019-03-15 18:37 ` [ruby-core:91850] " msiegel
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-73934.20180907150715.cb8f5e77b46be295@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).