# 11.1.5. Tracing Recursive Methods¶

In Java, the call stack keeps track of the methods that you have called since the main method executes. A stack is a way of organizing data that adds and removes items only from the top of the stack. An example is a stack of cups. You can grap a cup from the top of the stack or add more cups at the top of the stack.

When you are executing one method (method a) and it calls another method (method b) the method call is placed on the call stack along with information about where it was called from, which tells the run-time where to return to when the current method finishes executing. When method b finishes executing the run-time pops the method b off of the call stack and returns execution to the next line to be executed in method a.

Consider the following class definition. Figure 3: Code with a divide by zero in a method.¶

The code above will cause a run-time error of division by zero when it runs. The main method calls the method test1 (at line 20) which calls the method test2 (at line 6) which has the divide by zero error (line 14). This can be seen in the call stack shown below which shows the call stack from the top (most recent method) to the bottom (first method call). Figure 4: A call stack in DrJava with a run-time error¶

When a method calls itself the new method call gets added to the top of the call stack. Execution of the current method pauses while the recursive call is being processed. Each recursive call on the stack has its own set of local variables, including the parameter variables. The parameter values progressively change in each recursive call until we reach the base case which stops the recursion. Tracing Exercise

Let’s trace the execution of the factorial method defined below.

public static int factorial(int n)
{
if (n == 0)
return 1;
else
return n * factorial(n-1);
}


What happens when we call factorial(0)? It will return 1 (line 4) since n is equal to 0. How about factorial(1)? It will return 1 * factorial(0). We already know that factorial(0) returns 1, but the computer won’t remember that. It will execute factorial(0) and return the result (1). So factorial(1) returns 1 * 1 which is 1.

How can you show what is happening in a recursive call? Here is one way to do it. The lines below show the call stack upside down (with the bottom of the stack, or the beginning at the top and the most recent call at the bottom) for a call to factorial(5). This is a handy way to trace a recursive method on the exam and you will do much better on recursive problems if you practice doing it this way.

factorial(5) returns 5 * factorial(4)
factorial(4) returns 4 * factorial(3)
factorial(3) returns 3 * factorial(2)
factorial(2) returns 2 * factorial(1)
factorial(1) returns 1 * factorial(0)
factorial(0) returns 1


Once factorial(0) executes and returns 1 that value can be substituted back into the previous method call, starting at the top of the stack (shown at the bottom here) and working our way back to the bottom of the stack (shown at the top here).

factorial(5) returns 5 * factorial(4) = 5 * 24 = 120
factorial(4) returns 4 * factorial(3) = 4 * 6 = 24
factorial(3) returns 3 * factorial(2) = 2 so 3 * 2 = 6
factorial(2) returns 2 * factorial(1) = 1 so 2 * 1 = 2
factorial(1) returns 1 * factorial(0) = 1 so 1 * 1 = 1
factorial(0) returns 1


So factorial(5) returns 120.

You can step through this code using the Java Visualizer by clicking on this link: factorial.

Another way to see the call stack in action is to download and use the Jeloit software (see http://cs.joensuu.fi/jeliot/). Check your understanding

You can step through the code above using the Java Visualizer by clicking on the following link: Ex-11-3-2.

You can step through the code above using the Java Visualizer by clicking on the following link: Ex-11-3-3. Tracing Exercise

Let’s trace the execution of the bunny ears method defined below.

1public static int bunnyEars(int bunnies)
2{
3   if (bunnies == 0) return 0;
4   else if (bunnies == 1) return 2;
5   else return 2 + bunnyEars(bunnies - 1);
6}


What happens when we call bunnyEars(0)? It will return 0 since n is equal to 0 (line 3). How about bunnyEars(1)? It will return 2 since n is equal to 1 (line 4). What about bunnyEars(5)?

1bunnyEars(5) returns 2 + bunnyEars(4)
2bunnyEars(4) returns 2 + bunnyEars(3)
3bunnyEars(3) returns 2 + bunnyEars(2)
4bunnyEars(2) returns 2 + bunnyEars(1)
5bunnyEars(1) returns 2


This approach shows the call stack from bottom to top. Once bunnyEars(1) executes and returns 2 that value can be substituted back into the previous method call, starting at the top and working our way back toward the bottom (or beginning) of the call stack.

1bunnyEars(5) returns 2 + bunnyEars(4) = 2 + 8 = 10
2bunnyEars(4) returns 2 + bunnyEars(3) = 2 + 6 = 8
3bunnyEars(3) returns 2 + bunnyEars(2) = 2 + 4 = 6
4bunnyEars(2) returns 2 + bunnyEars(1) = 2 + 2 = 4
5bunnyEars(1) returns 2


So bunnyEars(5) returns 10. You can step through this code using the Java Visualizer by clicking on this link: bunnyEars. Check your understanding

You can step through the code above using the Java Visualizer by clicking on the following link: Ex-11-3-4.

You can step through the code above using the Java Visualizer by clicking on the following link: Ex-11-3-5

Continue to the next page for the Recursion lesson challenge and summary.