Building Distributed
Applications
Using the Progress AppServer


Remote Debugging

In remote debugging, the Debugger is initiated directly by 4GL code running in an AppServer session. Remote debugging is the only debugging mode that you can use to debug remote procedures that are:

This mode restricts your debugging activities to debugging only AppServer configuration and remote application procedures; you cannot debug any procedure in the client application session. It allows you to debug application code running on an Application Server process independently of the calling client application.

For example, an engineer who has developed a set of AppServer procedures does not have to examine the client code that his AppServer code will eventually support. When he is ready to debug his work, he only needs to examine his own code. In this situation, remote debugging is the ideal choice. When he debugs his code using this mode, he sees only his code on the Application Server process. If the Application Server process where the engineer has developed his code calls remote procedures on other Application Server process processes, he can also debug these other remote procedures using this mode.

In this debugging mode, the client application driving the Application Server process is unaware that the Debugger process is running on the Application Server process. That is, the procedure call stack only reveals entries up to the top level remote procedure call. It does not reveal anything about the client application.


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