stack-overflow

Being a beginner to C++ programming and computer systems architecture, I'm still learning the basics of C++. Yesterday I read about recursive function, so I decided to write my own, here's what I wrote : (very basic) int returnZero(int anyNumber) { if(anyNumber == 0) return 0; else { anyNumber--; return returnZero(anyNumber); } } And when I do this : int zero1 = returnZero(4793 ); it causes a stack overflow, however, if I pass the value 4792 as parameter, no overflow occurs. Any ideas as to why ? Whenever you call a function, including recursively, the return address and often the arguments

This question already has an answer here: What is a StackOverflowError? 13 answers I've looked everywhere and can't find a solid answer. According to the documentation, Java throws a java.lang.StackOverflowError error under the following circumstance: Thrown when a stack overflow occurs because an application recurses too deeply. But this raises two questions: Aren't there other ways for a stack overflow to occur, not only through recursion? Does the StackOverflowError happen before the JVM actually overflows the stack or after? To elaborate on the second question: When Java throws the

Please excuse what is probably a very basic question, but I am writing a program to store employee info and it works fine until it tries to set the info inside my employee class. It gives a stackoverflow error and I cannot figure out why. Thanks for any help. Main class: import java.util.Scanner; public class Main { public static void main(String[] args) { Scanner Input = new Scanner(System.in); System.out.println("Enter the number of employees to enter."); int employeeCount = Input.nextInt(); Input.nextLine(); Employee employee[] = new Employee[employeeCount]; String namesTemp; String

I am writing an application in Java using Swing. I am trying to implement functionality to save and load simulation states for at simulation i am running. The entire simulation is kept as an object, disconnected from Swing. I am trying to serialize my Simulation class with this code: public void saveSimulationState(String simulationFile) { try { Serializable object = this.sm; ObjectOutputStream objstream = new ObjectOutputStream(new FileOutputStream(simulationFile)); objstream.writeObject(object); objstream.close(); } catch (IOException e) { System.out.println(e.getMessage()); } } But i get

For example when we call say, a recursive function, the successive calls are stored in the stack. However, due to an error if it goes on infinitely the error is 'Segmentation fault' (as seen on GCC). Shouldn't it have been 'stack-overflow'? What then is the basic difference between the two? Btw, an explanation would be more helpful than wikipedia links (gone through that, but no answer to specific query). kennytm 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