Invalid working directory exception is not handled in node.js

[bengentil]

If the current working directory is invalid node fail to start.

It seems that the exception is never handled when calling process.cwd, at least in resolveArgv0 and evalScript (node.js:701 & node.js:414)

see TritonDataCenter/smartos-live#244 for more details

[daviddias]

I'm putting this one as future it should be rare to be running done from previously deleted paths. \cc @tjfontaine

[jasnell]

This is an edge case but testing shows that the behavior still occurs under v0.12 and io.js. Marking it as a lower priority tho.

[brendanashworth]

@jasnell are you sure you can reproduce this in io.js? I think nodejs/node#1194 fixed this.

[jasnell]

Will have to check again. May have been testing a down level build.
On Jun 17, 2015 12:33 AM, "Brendan Ashworth" notifications@github.com
wrote:

@jasnell https://github.com/jasnell are you sure you can reproduce this
in io.js? I think nodejs/node#1194
nodejs/node#1194 fixed this.

—
Reply to this email directly or view it on GitHub
#6060 (comment).

[jasnell]

finally getting back to this, yes, this is resolved in v3.x. Can potentially backport nodejs/node#1194 to v0.12 if necessary but given the lack of priority on this, I'm inclined to close here.