From: shibata.hiroshi@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:65701] [ruby-trunk - Bug #10290] segfault when calling a lambda recursively after rescuing SystemStackError
Date: Tue, 14 Oct 2014 12:02:58 +0000 [thread overview]
Message-ID: <redmine.journal-49429.20141014120258.35778f3a69ed761c@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-10290.20140924062037@ruby-lang.org
Issue #10290 has been updated by Hiroshi SHIBATA.
I can reproduce clang on linux.
```
[hsbt@chkbuild001 ~]$ clang -v
clang version 3.5.0 (tags/RELEASE_350/final)
Target: x86_64-amazon-linux-gnu
Thread model: posix
Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-amazon-linux/4.8.2
Found candidate GCC installation: /usr/lib/gcc/x86_64-amazon-linux/4.8.2
Selected GCC installation: /usr/bin/../lib/gcc/x86_64-amazon-linux/4.8.2
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64
```
----------------------------------------
Bug #10290: segfault when calling a lambda recursively after rescuing SystemStackError
https://bugs.ruby-lang.org/issues/10290#change-49429
* Author: Jack Nagel
* Status: Feedback
* Priority: Normal
* Assignee:
* Category:
* Target version:
* ruby -v: ruby 2.1.3p242 (2014-09-19 revision 47629) [x86_64-darwin13.0]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The following code segfaults on Ruby 2.1.3:
```
l = -> { l.() }
begin
l.()
rescue SystemStackError
l.() # segfault
end
```
the issue does not occur on trunk.
---Files--------------------------------
ruby_2014-09-25-000925_haswell.log (46.4 KB)
ruby_2014-09-25-001644_haswell.log (46.8 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2014-10-14 12:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-10290.20140924062037@ruby-lang.org>
2014-09-24 6:20 ` [ruby-core:65254] [ruby-trunk - Bug #10290] [Open] segfault when calling a lambda recursively after rescuing SystemStackError jacknagel
2014-09-24 6:28 ` [ruby-core:65255] [ruby-trunk - Bug #10290] " jacknagel
2014-09-25 5:11 ` [ruby-core:65267] " jacknagel
2014-09-25 5:18 ` [ruby-core:65268] " jacknagel
2014-09-26 5:45 ` [ruby-core:65279] " nobu
2014-10-13 7:37 ` [ruby-core:65650] [ruby-trunk - Bug #10290] [Feedback] " shibata.hiroshi
2014-10-13 17:16 ` [ruby-core:65678] [ruby-trunk - Bug #10290] " jacknagel
2014-10-14 1:49 ` [ruby-core:65688] " shibata.hiroshi
2014-10-14 12:02 ` shibata.hiroshi [this message]
2014-10-16 1:41 ` [ruby-core:65738] " jacknagel
2014-10-16 5:22 ` [ruby-core:65752] " nobu
2016-09-19 7:48 ` [ruby-core:77310] [Ruby trunk Bug#10290] " johncbackus
2016-09-20 0:48 ` [ruby-core:77317] " nobu
2016-09-22 7:24 ` [ruby-core:77351] " johncbackus
2016-11-25 13:28 ` [ruby-core:78360] [Ruby trunk Bug#10290][Assigned] " shyouhei
2017-05-11 5:47 ` [ruby-core:81099] [Ruby trunk Bug#10290] " johncbackus
2017-05-12 6:27 ` [ruby-core:81114] " nobu
2017-05-12 7:54 ` [ruby-core:81124] " johncbackus
2017-06-16 9:47 ` [ruby-core:81710] " nobu
2019-08-20 20:20 ` [ruby-core:94449] [Ruby master " merch-redmine
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-49429.20141014120258.35778f3a69ed761c@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).