ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: kiyoka@sumibi.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:68637] [Ruby trunk - Bug #11001] [Open] 2.2.1 Segmentation fault in reserve_stack() function.
Date: Wed, 25 Mar 2015 14:04:54 +0000	[thread overview]
Message-ID: <redmine.issue-11001.20150325140453.8b1c1e70bc99d957@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11001.20150325140453@ruby-lang.org

Issue #11001 has been reported by Kiyoka Nishiyama.

----------------------------------------
Bug #11001: 2.2.1 Segmentation fault in reserve_stack() function.
https://bugs.ruby-lang.org/issues/11001

* Author: Kiyoka Nishiyama
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
SEGV depends on stack limit size with 'ulimit -s <size>' .

This shell script [ulimit_change_test.sh] can reproduce SEGV on my Debian environment.
my Linux environment is Debian/GNU Linux 7.8.
But, I cannot reproduce this SEGV on Amazon Linux environment.

result on Debian 7.8
~~~
 $ /tmp/ulimit_change_test.sh 
8515
/tmp/ulimit_change_test.sh: 3 行: 20470 Segmentation fault      ./ruby --version
8514
/tmp/ulimit_change_test.sh: 3 行: 20471 Segmentation fault      ./ruby --version
8513
/tmp/ulimit_change_test.sh: 3 行: 20472 Segmentation fault      ./ruby --version
8512
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
8511
/tmp/ulimit_change_test.sh: 3 行: 20475 Segmentation fault      ./ruby --version
8510
/tmp/ulimit_change_test.sh: 3 行: 20476 Segmentation fault      ./ruby --version
8509
/tmp/ulimit_change_test.sh: 3 行: 20477 Segmentation fault      ./ruby --version
8508
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
8507
/tmp/ulimit_change_test.sh: 3 行: 20480 Segmentation fault      ./ruby --version
8506
/tmp/ulimit_change_test.sh: 3 行: 20481 Segmentation fault      ./ruby --version
8505
/tmp/ulimit_change_test.sh: 3 行: 20482 Segmentation fault      ./ruby --version
8504
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
8503
/tmp/ulimit_change_test.sh: 3 行: 20485 Segmentation fault      ./ruby --version
8502
/tmp/ulimit_change_test.sh: 3 行: 20486 Segmentation fault      ./ruby --version
8501
/tmp/ulimit_change_test.sh: 3 行: 20487 Segmentation fault      ./ruby --version
8500
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
8499
/tmp/ulimit_change_test.sh: 3 行: 20490 Segmentation fault      ./ruby --version
8498
/tmp/ulimit_change_test.sh: 3 行: 20491 Segmentation fault      ./ruby --version
8497
/tmp/ulimit_change_test.sh: 3 行: 20492 Segmentation fault      ./ruby --version
8496
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
8495
/tmp/ulimit_change_test.sh: 3 行: 20495 Segmentation fault      ./ruby --version
8494
/tmp/ulimit_change_test.sh: 3 行: 20496 Segmentation fault      ./ruby --version
8493
/tmp/ulimit_change_test.sh: 3 行: 20497 Segmentation fault      ./ruby --version
8492
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-linux]
8491
/tmp/ulimit_change_test.sh: 3 行: 20500 Segmentation fault      ./ruby --version
8490
/tmp/ulimit_change_test.sh: 3 行: 20501 Segmentation fault      ./ruby --version
8489
/tmp/ulimit_change_test.sh: 3 行: 20502 Segmentation fault      ./ruby --version
 $ 
~~~

This SEGV occurs in reserve_stack() function.
I suspect that the buf[0x100] size is too small for margin.
I attached patch to fix it.


---Files--------------------------------
0001-Bugfix-patch-of-reserve_stack-function.patch (720 Bytes)
ulimit_change_test.sh (211 Bytes)


-- 
https://bugs.ruby-lang.org/

       reply	other threads:[~2015-03-25 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11001.20150325140453@ruby-lang.org>
2015-03-25 14:04 ` kiyoka [this message]
2015-06-04  1:52 ` [ruby-core:69460] [Ruby trunk - Bug #11001] 2.2.1 Segmentation fault in reserve_stack() function wingicelee
2015-06-04  9:49 ` [ruby-core:69462] [Ruby trunk - Bug #11001] [Feedback] " nobu
2015-06-27  4:49 ` [ruby-core:69751] [Ruby trunk - Bug #11001] " kubo
2015-06-27  6:08   ` [ruby-core:69752] " Eric Wong
2015-06-27 23:38     ` [ruby-core:69758] " SASADA Koichi
2015-06-28  1:33 ` [ruby-core:69759] " nobu
2015-06-28  5:26 ` [ruby-core:69760] " kubo

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.issue-11001.20150325140453.8b1c1e70bc99d957@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).