The Call Stack tab displays the stack frames for the currently suspended thread. If the debuggee is running or if the current thread is a zombie thread (one that is finished executing but is still listed in the Threads tab), the call stack pane will be empty.
Appropriately, the top most stack frame corresponds to the top most frame displayed in the Call Stack table. Each stack frame is assigned a stack position number where one is the bottom most position and the larger the number, the closer that frame is to the top.
The current stack frame will be the one with a yellow arrow pointing next to it. To change the current stack frame, double-click on the frame you wish to become current. Doing so will cause the source file for that stack frame to opened if it hasn't already been opened and make the line where the frame is at visible in the source viewer. If file could not be found, an error message will be displayed on the status bar.
Hint: Double-clicking on an already current stack frame is a quick way to jump back to the location of that frame in the source view
Number Column
This column displays the frame's stack position number. Frame positions are numbered from one. The frame at position one represents the bottom of the stack where as the frame with the largest stack position is the top most stack frame, where the most recently executing method is located.
Location Column
The format of the stack frame location strings is fully-qualified classname followed by method name (Class's simple name : line number). If a stack frame is currently executing within a native method, the words "Native Method" will appear instead of displaying the current line number.
If the original source file name or line number is not available because the .class file was not compiled with debug information or has been stripped of all debug information, two double question marks will appear in its place to indicate this value is unknown. If either one of these debug information is missing, BugSeeker will be unable to jump to the location of the stack frame's location in the source viewer. More details on how to compile a class with debug information is provide at Compiling Classes with Debug Information section of this manual.
Save to file
You can save the current list of stack frame locations to a text file on disk anytime the current debug session is paused. Right-click anywhere within the Call Stack tab and select Save to File and you will be prompted for the save location. The Save to File feature is disabled whenever the debuggee is running.