VM: options.columnOffset has no effect on column number in stack trace output #26780
Closed
Description
- Version: v10.3.0 and v10.15.2
- Platform: Linux ip-172-30-3-105 4.14.42-52.37.amzn1.x86_64
- Subsystem: vm
In vm.runInNewContext (and maybe other versions of "run", too), the options.columnOffset has no effect. I've tried a couple of intentionally-caused errors with various columnOffset values (ranging from -5 to 5), but the character position reported in the stack trace (via e.stack) is always the same. Note that lineOffset works as expected.