uncaught exceptions' stack traces aren't being printed

[jonathanong]

super annoying to debug =/

[dougwilson]

yep

[boneskull]

@jonathanong Do we know what caused this?

[jonathanong]

if i knew i would fix it!

[travisjeffery]

is this related to this #1198 ? may be fixed in the latest version.

[boneskull]

@travisjeffery Doesn't appear to be. I reverted the change and am still not getting a full stack.

[boneskull]

OK, this has been an issue for a long time. I checked as early as v1.10.0 and it's still there. This seems to only affect the "maximum call stack size exceeded" RangeError; other uncaught errors still give a proper trace.

So if I had to hazard a guess, NodeJS could do a better job of telling the user exactly where the recursive error happened.

I'm not sure there's anything to do here.

[travisjeffery]

👍 for node handling this better

[boneskull]

@travisjeffery To test the plain ol' uncaught exceptions, I followed the directions in uncaught.js and observed the results.

To test maximum call stack size exceeded, I appended this test to the same file:

  it('should give you a proper stack trace if recursive error', function (done) {
    process.nextTick(function notDone() {
      notDone();
    })
  });

I found this SO thread and I'm thinking we're SOL here.

[boneskull]

(fwiw I tried this under NodeJS v0.11.13 and it still doesn't work)

[travisjeffery]

alright we might as well close this here i guess