From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:67009] [ruby-trunk - Bug #10460] Segfault instead of stack level too deep
Date: Sun, 21 Dec 2014 01:06:45 +0000 [thread overview]
Message-ID: <redmine.journal-50537.20141221010645.c91c5f669c93f06c@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-10460.20141030131734@ruby-lang.org
Issue #10460 has been updated by Nobuyoshi Nakada.
Duplicated by Bug #10626: BUS error from nesting lambda's and calls to methods defined with define_method added
----------------------------------------
Bug #10460: Segfault instead of stack level too deep
https://bugs.ruby-lang.org/issues/10460#change-50537
* Author: Arne Brasseur
* Status: Open
* Priority: High
* Assignee: Nobuyoshi Nakada
* Category: core
* Target version: current: 2.2.0
* ruby -v: ruby 2.2.0dev (2014-10-29 trunk 48188) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The code to trigger this can be found here: https://gist.github.com/mbj/31163a8e712573877268
Also have a look at the comments there. A lot of different people tried it, in some cases it segfaults, in others it doesn't. It seems to have to do with version of gcc or specific CFLAGS.
I can reproduce the problem for 2.1.3, 2.1.4, and trunk.
---Files--------------------------------
rspec_ruby_segfault.rb (233 Bytes)
sample_output (26 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2014-12-21 1:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-10460.20141030131734@ruby-lang.org>
2014-10-30 13:17 ` [ruby-core:66023] [ruby-trunk - Bug #10460] [Open] Segfault instead of stack level too deep arne
2014-11-04 9:43 ` [ruby-core:66075] [ruby-trunk - Bug #10460] " arne
2014-11-12 4:17 ` [ruby-core:66219] " a_lamothe
2014-11-18 13:53 ` [ruby-core:66345] " arne
2014-11-19 7:51 ` [ruby-core:66358] " Eric Wong
2014-11-19 7:58 ` [ruby-core:66359] " normalperson
2014-11-19 21:13 ` [ruby-core:66365] " arne
2014-11-19 21:26 ` [ruby-core:66366] " Eric Wong
2014-11-19 21:28 ` [ruby-core:66367] " normalperson
2014-11-26 22:33 ` [ruby-core:66497] " andrewm.bpi
2014-11-27 11:23 ` [ruby-core:66520] " ko1
2014-12-03 13:58 ` [ruby-core:66659] " v.ondruch
2014-12-21 1:06 ` nobu [this message]
2015-02-09 14:17 ` [ruby-core:68074] [Ruby trunk " arne
2015-06-26 10:16 ` [ruby-core:69742] " contact
2019-08-21 3:52 ` [ruby-core:94454] [Ruby master Bug#10460] " 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-50537.20141221010645.c91c5f669c93f06c@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).