I believe the problem is that your array is on the stack, and that your compiler is too old to support over-aligned stack variables. GCC 4.6 and later fixed that bug. C11/C++11 alignas(64) float a[4]; Just Works for any power of 2 alignment. So does the GNU C __attribute__((aligned(x))) as you were using it. (In … Read more
You can do this with a trace function (props to Spacedman for improving the original version of this to trace returns and use some nice indenting): def tracefunc(frame, event, arg, indent=[0]): if event == “call”: indent[0] += 2 print(“-” * indent[0] + “> call function”, frame.f_code.co_name) elif event == “return”: print(“<” + “-” * indent[0], … Read more
I think primarily you’re getting confused between a program’s stack and any old stack. A Stack Is an abstract data structure which consists of information in a Last In First Out system. You put arbitrary objects onto the stack and then you take them off again, much like an in/out tray, the top item is … Read more
You should wrap your recursive function call into a setTimeout, setImmediate or process.nextTick function to give node.js the chance to clear the stack. If you don’t do that and there are many loops without any real async function call or if you do not wait for the callback, your RangeError: Maximum call stack size exceeded … Read more
Seems like there is an UI-Bug in the Android Studio (1.x, 2.x and 3.x). For me the “Frames/Threads” Panel was completely hidden behind the toolbar, so I had to change the size from the “variable” panel by dragging its left border to reveal the “Frames/Threads”. [I have to admit, that @Greg added this picture after … Read more
Check for any recusive calls for methods. Mainly it is caused when there is recursive call for a method. A simple example is public static void main(String… args) { Main main = new Main(); main.testMethod(1); } public void testMethod(int i) { testMethod(i); System.out.println(i); } Here the System.out.println(i); will be repeatedly pushed to stack when the … Read more
Stack growth doesn’t usually depend on the operating system itself, but on the processor it’s running on. Solaris, for example, runs on x86 and SPARC. Mac OSX (as you mentioned) runs on PPC and x86. Linux runs on everything from my big honkin’ System z at work to a puny little wristwatch. If the CPU … Read more
The call stack could also be called a frame stack. The things that are stacked after the LIFO principle are not the local variables but the entire stack frames (“calls”) of the functions being called. The local variables are pushed and popped together with those frames in the so-called function prologue and epilogue, respectively. Inside … Read more
To disable these, use the gcc option -fno-asynchronous-unwind-tables -fno-dwarf2-cfi-asm may be needed also.
For a linux-only solution you can use backtrace(3) that simply returns an array of void * (in fact each of these point to the return address from the corresponding stack frame). To translate these to something of use, there’s backtrace_symbols(3). Pay attention to the notes section in backtrace(3): The symbol names may be unavailable without … Read more