Feedback
Did this article resolve your question/issue?

   

Article

Debugger not showing available temp-tables of dataset-handle passed to subprocedure.

Information

 
TitleDebugger not showing available temp-tables of dataset-handle passed to subprocedure.
URL NameDebugger-not-showing-available-temp-tables-of-datasethandle-passed-to-subprocedure
Article Number000138464
EnvironmentProduct: OpenEdge
Version: 11.7.x
OS: Windows
Other: Standalone debugger
Question/Problem Description
Customer has a large application. The application is being written in Progeess Developer Studio for OpenEdge (PDS for OpenEdge). For debugging purposes, the developer has added the ABL statements DEBUGGER:INITIATE() and DEBUGGER:SET-BREAK(), for setting a break-point in his code. The developer then steps into a few layers. At this stage, in a subprocedure, a dataset was passed into the subprocedure as a dataset-handle. The developer attempts to view the buffers or temp-tables of the dataset-handle through the debugger as follows:

Shows the view buttons on the standalone debugger.

When one of the buffers or temp-tables is selected and the Dataview menu option is selected, an error message appears with the following message:

<table name> is an invalid buffer reference. The same message appears whether the buffer or temp-tables button is selected.

Shows the error message that pops up.

If the variables button is selected, a temp-table handle value has been assigned to a handle variable and the Dataview menu option is selected, the fields and values of the temp-table are viewable. 

Shows the fields displayed from the variables window.
 
Steps to Reproduce
Clarifying Information
Application is developed in PDS for OpenEdge.
The application is being tested by using the Run External Tools option of the PDS for OpenEdge tool bar and an ant script is run that starts prowin which runs the application.
DEBUGGER:INITIATE and DEBUGGER:SET-BREAK statements are included in the source code to set an initial breakpoint and start up the standalone debugger.
Error Message<table name> is an invalid buffer reference.
Defect/Enhancement Number
Cause
The exact cause is not known at this time.
This is thought to be a limitation of the standalone debugger.
Resolution
None at this time.
Workaround
Use the debugger that is built into PDS for OpenEdge. The debugger in PDS for OpenEdge does not issue the error message when the buffers are selected and the attributes and values are displayed.
Notes
References to other Documentation:

Progress article(s):

 How to insert a hard break point in a program to launch the StandAlone Debugger?
Last Modified Date11/20/2020 7:05 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.