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.
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, runsremote.p
, andremote.p
, line 3 runsdistant.p
and you are stepping through line 17, the SHOW STACK displays the following information.
The following list notes other observations to keep in mind when using distributed debugging:
- Because the Debugger is initiated by the root client application, a version of the
prodebug
executable does not have to be running on the Application Server process that you are debugging.- The root client application must run in an environment that supports the Debugger. For example, if your root client application is on a UNIX platform, you need to have Motif running on that platform so that you can display and use the Debugger Window. (On UNIX, the Debugger is a Motif application.)
- You can only examine variables within an AppServer session when code is being executed on the AppServer as indicated by the procedure call stack.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |