On Tue, 6 Aug 2019 12:34:55 -0400 Steven Rostedt <[email protected]> wrote:
> Here's the best way to explain this. The code is using the stack trace > to figure out which function is the stack hog. Or perhaps a serious of Why so serious? .... s/serious/series/ -- Steve > stack hogs. On x86, a call stores the return address as it calls the > next function. Then that function allocates its stack frame for its > local variables and saving of registers.
