Hacker News Reader

Comment by austin-cheney | Hacker News Reader

The common answer is a stack trace. In JavaScript you can get that any time and any where with:

    new Error().stack;

Stack traces lose their helpfulness in applications with high frequency network traffic because the network buffer will likely not be the start of flow control but a stack trace cannot run deeper than that.

View on HN

// new Error().stack;

or just console.trace()

I realized I do not understand how function calls use stack (exactly and accurately I mean I can imagine some stack push pop happening). Any guidance for resources? I seeked in google but turns out most materials are related to assembly language programming which I have no idea about.

A stack trace just lists the steps an application went through by calls to non primitive references. This varies pretty significantly by language. An item in the stack is a step in memory. That is about as much as I know.

Reply on news.ycombinator.com