From: usa@garbagecollect.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:73673] [Ruby trunk Bug#11851] rb_profile_frames() causes segmentation fault
Date: Wed, 03 Feb 2016 10:37:31 +0000 [thread overview]
Message-ID: <redmine.journal-56865.20160203103730.1c73231e85c20513@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11851.20151220085808@ruby-lang.org
Issue #11851 has been updated by Usaku NAKAMURA.
Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN to 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONTNEED
----------------------------------------
Bug #11851: rb_profile_frames() causes segmentation fault
https://bugs.ruby-lang.org/issues/11851#change-56865
* Author: Kazuki Yamaguchi
* Status: Closed
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.3.0dev (2015-12-20 trunk 53215) [x86_64-linux]
* Backport: 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONTNEED
----------------------------------------
When the control frame stack contains an ifunc-frame, calling rb_profile_frames() causes a segmentation fault.
I've attached a patch that changes it to ignore ifunc frames as it did previously.
---Files--------------------------------
0001-vm_backtrace.c-rb_profile_frames-ignore-ifunc-frames.patch (1.36 KB)
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2016-02-03 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11851.20151220085808@ruby-lang.org>
2015-12-20 8:58 ` [ruby-core:72409] [Ruby trunk - Bug #11851] [Open] rb_profile_frames() causes segmentation fault k
2015-12-20 11:48 ` [ruby-core:72410] [Ruby trunk - Bug #11851] " nobu
2015-12-20 12:57 ` [ruby-core:72412] " k
2016-02-03 10:37 ` usa [this message]
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-56865.20160203103730.1c73231e85c20513@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).