error on Windows

[mcollina]

Error: Encountered an unparseable frame "(anonymous) D:\a

[AlanSl]

Can you post the full file / directory path (what's being chopped after the a) and I'll add it to the edge cases / tests PR I'm working on, which includes a lot of funky stuff with Windows paths, Unicode etc

[AlanSl]

Also which version of Node? The fix for Windows path separators being treated as escape patterns has some issues in Node 8 and different issues in Node 11 that aren't in Node 10

[davidmarkclements]

I spoke to @mcollina just now – it's Node 10 (and Windows 10)

if it's in the latest 0x release, #201 might be related

[mcollina]

I think the regexp introduced in #193

is not complete/broken on Node 10.

cc @mafintosh

[mcollina]

I think this line

0x/lib/v8-log-to-ticks.js

Line 36 in 1cfbc56

const startPath = line.indexOf(':\\')

needs to change the pattern from :\\ to :\

[AlanSl]

There's a bunch of issues with that regex that are fixed in the PR I'm working on, for instance it gets confused by unicode chars like //u12a3 - but in my tests I've only seen that happen on Node 8. What's the text after the a in your path?

Maybe it's mistakenly parsing something like D:/a/n as a newline?

[mcollina]

That happens on Azure pipelines. There is nothing else.

[davidmarkclements]

was this ever resolved?

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.