1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[PRISM] Eval frames should not have an absolute path

Browse Source
This commit is contained in:
Kevin Newton 2024-02-21 15:27:11 -05:00
parent fce780473c
commit 80ffa3006c
2 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
test/.excludes-prism/TestProfileFrames.rb
View File

@ -1 +0,0 @@
exclude(:test_profile_frames, "unknown")

2
vm_eval.c
View File

@ -1736,7 +1736,7 @@ pm_eval_make_iseq(VALUE src, VALUE fname, int line,
iseq = ISEQ_BODY(iseq)->parent_iseq;
}
iseq = pm_iseq_new_eval(&result.node, name, fname, fname, line, parent, 0);
iseq = pm_iseq_new_eval(&result.node, name, fname, Qnil, line, parent, 0);
pm_scope_node_t *prev = result.node.previous;
while (prev) {