[PRISM] Eval frames should not have an absolute path

ruby · Feb 21, 2024 · 80ffa30 · 80ffa30
1 parent fce7804
commit 80ffa30
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/test/.excludes-prism/TestProfileFrames.rb b/test/.excludes-prism/TestProfileFrames.rb
diff --git a/vm_eval.c b/vm_eval.c
@@ -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) {