Handling a stack overflow is not the right solution, instead, you must ensure that your program does not overflow the stack. Do not allocate large variables on the stack (where what is “large” depends on the program). Ensure that any recursive algorithm terminates after a known maximum depth. If a recursive algorithm may recurse an … Read more
From Wikipedia: In software, a stack overflow occurs when too much memory is used on the call stack. In many programming languages, the call stack contains a limited amount of memory, usually determined at the start of the program. The stack is a data structure that keeps record of the point the subroutines of a … Read more
The hash code for conforming List implementations has been specified in the interface: Returns the hash code value for this list. The hash code of a list is defined to be the result of the following calculation: int hashCode = 1; for (E e : list) hashCode = 31*hashCode + (e==null ? 0 : e.hashCode()); … Read more
Stack overflow is [a] cause, segmentation fault is the result. At least on x86 and ARM, the “stack” is a piece of memory reserved for placing local variables and return addresses of function calls. When the stack is exhausted, the memory outside of the reserved area will be accessed. But the app did not ask … Read more
The JVM has an artificial limit of 1024 entries that you can have in the stack trace of an Exception or Error, probably to save memory when it occurs (since the VM has to allocate memory to store the stack trace). Fortunately, there is a flag that allows to increase this limit. Just run your … Read more
In the standard/stock GCC, stack protector is off by default. However, some Linux distributions have patched GCC to turn it on by default. In my opinion, this is rather harmful, as it breaks the ability to compile anything that’s not linked against the standard userspace libraries unless the Makefile specifically disables stack protector. It would … Read more
This question is a bit old, but I just found a nice way of getting the stack trace of my application just before overflowing and I would like share it with other googlers out there: When your ASP.NET app crashes, a set of debugging files are dumped in a “crash folder” inside this main folder: … Read more
Whenever a TypeInitializationException is thrown, check all initialization logic of the type you are referring to for the first time in the statement where the exception is thrown – in your case: Logger. Initialization logic includes: the type’s static constructor (which – if I didn’t miss it – you do not have for Logger) and … Read more
Unfortunately, Java’s builtin regex support has problems with regexes containing repetitive alternative paths (that is, (A|B)*). This is compiled into a recursive call, which results in a StackOverflow error when used on a very large string. A possible solution is to rewrite your regex to not use a repititive alternative, but if your goal is … Read more
This is clearly JVM- and possibly also architecture-specific. I’ve measured the following: static int i = 0; public static void rec0() { i++; rec0(); } public static void main(String[] args) { … try { i = 0; rec0(); } catch (StackOverflowError e) { System.out.println(i); } … } using Java(TM) SE Runtime Environment (build 1.7.0_09-b05) Java … Read more