If you woke up in the morning and you wanted to drive to the store, you would have to do several things. Obviously, you would need to get in the car first. But to get into the car, you would need to find

A call stack is simply the listing of functions that have been called up to a certain point. As your program runs, it will execute functions, and each of those functions may themselves call other functions. Every time a function is called, it is basically added to the top of a stack (like a stack of dinner plates). Once a function has finished executing, it is removed from the stack. Using a function call stack, you can quickly see the order of execution of your program (at that point in time).

If you woke up in the morning and you wanted to drive to the store, you would have to do several things. Obviously, you would need to get in the car first. But to get into the car, you would need to find your car keys. To find the car keys, you'd have to get up out of bed. Your call stack for that might look like:

1. Drive to store (the current thing you're doing)
2. Get into the car
3. Find car keys
4. Get out of bed (the first thing you did)

In call stacks, you read from the bottom to the top. So in your screenshot, you have three lines, which basically tell me that on line 72 of listing.021.php, you have code that tries to create a new CdProduct.

Then, in your CdProduct constructor (on line 34 of that same listing.021.php file), you create a new ShopProduct.

The call stack is finally showing that you are currently looking at line 10 in that file, and you're in the ShopProduct constructor.

Introduction
Many web sites contain image galleries; a common design for these galleries includes a page with a collection of thumbnail images. You can click on each of the thumbnail images to see the larger version of the image. This is easily i…