debugging - getting the list of all functions executed like call stack in asp.net -

I'm having trouble debugging a problem coming to our website. This is the problem. I have a webpage that includes information related to employee and photograph of employee. When the user logs in to our website, we are depositing the details of the employee in the session. I am setting the following image URL for the picture of an employee.

  imgEEPhoto.ImageUrl = imgPhoto.aspx? Company = XXXX & amp; Empno = YYYY  

Inside page imgPhoto.aspx, I'm checking whether the session is live for that user or not. When I log in to the page in which there is an employee's picture, then the photo is never displayed. That's because I'm checking whether the session is alive within the imgPhoto.aspx page or not. Sometimes the session is alive and sometimes the session does not survive. It seems that there is such a function which is setting the session to zero asynchronously, I do not know how to track that function I am So I think that inside the imgPhoto.aspx page, if I can get a list of all functions executed so far, then I can track the function to reset the session. Is there a way to find it?

If there is no other way to debug this problem, please let me know.

Edit:

Page imgphoto. Aspx gets the company and empno query string as the parameter then the page receives binary data based on company and ammo and uses the response. BinaryWrite () Checking session to display photos is at the beginning of this function. Therefore, this function is called elsewhere and after the completion of all the functions in the home the session is ending. Actually, I'm not sure that this is being time-out because I can print the session. But I can not access the variable stored in the session

If I print the callstack inside the function, then it is giving the list of functions that are implemented inside that page. It is not giving up those tasks which are executed before that ceremony.

There is no built-in feature. NET is asked to list all tasks, though You can print a call-stack at a specific point (such as what the exceptions do).

If it wants you to take the route.