-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
VM: options.columnOffset has no effect on column number in stack trace output #26780
Copy link
Copy link
Closed
Labels
docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.help wantedIssues that need assistance from volunteers or PRs that need help to proceed.Issues that need assistance from volunteers or PRs that need help to proceed.questionIssues asking questions about Node.js.Issues asking questions about Node.js.vmIssues and PRs related to the vm subsystem.Issues and PRs related to the vm subsystem.
Description
Activity
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.help wantedIssues that need assistance from volunteers or PRs that need help to proceed.Issues that need assistance from volunteers or PRs that need help to proceed.questionIssues asking questions about Node.js.Issues asking questions about Node.js.vmIssues and PRs related to the vm subsystem.Issues and PRs related to the vm subsystem.
In vm.runInNewContext (and maybe other versions of "run", too), the
options.columnOffsethas no effect. I've tried a couple of intentionally-caused errors with variouscolumnOffsetvalues (ranging from -5 to 5), but the character position reported in the stack trace (viae.stack) is always the same. Note thatlineOffsetworks as expected.