* [ruby-core:72409] [Ruby trunk - Bug #11851] [Open] rb_profile_frames() causes segmentation fault
[not found] <redmine.issue-11851.20151220085808@ruby-lang.org>
@ 2015-12-20 8:58 ` k
2015-12-20 11:48 ` [ruby-core:72410] [Ruby trunk - Bug #11851] " nobu
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: k @ 2015-12-20 8:58 UTC (permalink / raw)
To: ruby-core
Issue #11851 has been reported by Kazuki Yamaguchi.
----------------------------------------
Bug #11851: rb_profile_frames() causes segmentation fault
https://bugs.ruby-lang.org/issues/11851
* Author: Kazuki Yamaguchi
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.3.0dev (2015-12-20 trunk 53215) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ruby-core:72410] [Ruby trunk - Bug #11851] rb_profile_frames() causes segmentation fault
[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 ` nobu
2015-12-20 12:57 ` [ruby-core:72412] " k
2016-02-03 10:37 ` [ruby-core:73673] [Ruby trunk Bug#11851] " usa
3 siblings, 0 replies; 4+ messages in thread
From: nobu @ 2015-12-20 11:48 UTC (permalink / raw)
To: ruby-core
Issue #11851 has been updated by Nobuyoshi Nakada.
Could you show reproducible code or add a test?
----------------------------------------
Bug #11851: rb_profile_frames() causes segmentation fault
https://bugs.ruby-lang.org/issues/11851#change-55697
* Author: Kazuki Yamaguchi
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.3.0dev (2015-12-20 trunk 53215) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ruby-core:72412] [Ruby trunk - Bug #11851] rb_profile_frames() causes segmentation fault
[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 ` k
2016-02-03 10:37 ` [ruby-core:73673] [Ruby trunk Bug#11851] " usa
3 siblings, 0 replies; 4+ messages in thread
From: k @ 2015-12-20 12:57 UTC (permalink / raw)
To: ruby-core
Issue #11851 has been updated by Kazuki Yamaguchi.
Uploaded reproducible code to Gist: https://gist.github.com/rhenium/e3a179b0cac87606c183
This runs on Ruby 2.2.4 and patched trunk but segfaults on trunk.
----------------------------------------
Bug #11851: rb_profile_frames() causes segmentation fault
https://bugs.ruby-lang.org/issues/11851#change-55699
* Author: Kazuki Yamaguchi
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.3.0dev (2015-12-20 trunk 53215) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ruby-core:73673] [Ruby trunk Bug#11851] rb_profile_frames() causes segmentation fault
[not found] <redmine.issue-11851.20151220085808@ruby-lang.org>
` (2 preceding siblings ...)
2015-12-20 12:57 ` [ruby-core:72412] " k
@ 2016-02-03 10:37 ` usa
3 siblings, 0 replies; 4+ messages in thread
From: usa @ 2016-02-03 10:37 UTC (permalink / raw)
To: ruby-core
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-02-03 10:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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 ` [ruby-core:73673] [Ruby trunk Bug#11851] " usa
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).