Long stack traces

[floatdrop]

When using stackman with long stacktraces it gives empty frames:

{ properties: {}, frames: [] }

var Promise = require('bluebird');
var stackman = require('stackman')();

Promise.longStackTraces();
Promise.resolve().then(function outer() {
    return Promise.resolve().then(function inner() {
        return Promise.resolve().then(function evenMoreInner() {
            a.b.c.d()
        }).catch(function catcher(e) {
            stackman(e, function (stack) {
                console.log(stack);
            });
        });
    });
});

[watson]

@floatdrop Interesting... Thanks for the bug report :) I'll look into it

[floatdrop]

@watson I just realized, that example was wrong - var stackman = require('stackman')(); should come after bluebird require, but result is same (fixed example in topic).

[watson]

I've been working on different ways of getting around this issue, but so far haven't found a good solution. The issue is that the error catcher in bluebird get's a hold of and manipulates the error object before it passes it to the catcher function. At that point the stack trace is already generated and stackman and lost the window in which to get access to it.

I currently do not recommend running with any form of long stack trace system in production anyway since it decreases performance (which is also the recommendation by the bluebird module).

Until there is a stable solution for having multiple modules attempting to hook in to the V8 stack trace engine this is not something that can be supported. I would love to hear if anybody else have found a way around this issue?