Building Distributed
Applications
Using the Progress AppServer


About the Debugger Window

When you are using distributed debugging, the Debugger window and the procedure call stack help orient you to the procedures available to debug. For example, the title bar of the Debugger Listing Panel changes as you change the procedures that you are debugging. Table 7–1 indicates the dynamic information changes that occur in the title bar.

Table 7–1: Content of the Debugger Listing Panel Title Bar 
When you are stepping through a...
Then the title bar reads...
Local procedure, such as example.p
example.p (LOCAL)
Remote procedure, such as remote.p, on an Application Server process whose server handle’s NAME attribute is RemoteServer1
remote.p (ON SERVER RemoteServer1)
Remote procedure, such as distant.p, on an Application Server process whose server handle’s NAME attribute is RemoteServer2, which was run from a procedure on RemoteServer1 (RemoteServer2 is an Application Server process once removed from the root client application.)
distant.p (ON SERVER RemoteServer2 via RemoteServer1)

The procedure call stack reflects the entire call stack for the distributed application. That is, the SHOW STACK command displays location information for each procedure call stack entry.

For example, if example.p, line 4, runs remote.p, and remote.p, line 3 runs distant.p and you are stepping through line 17, the SHOW STACK displays the following information.

example.p():4
remote.p(...):3 ON SERVER RemoteServer1
distant.p(...):17 ON SERVER RemoteServer2 Via RemoteServer1 

The following list notes other observations to keep in mind when using distributed debugging:


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095