Need tips on debugging possible memory-leak
Need tips on debugging possible memory-leak
(OP)
We have a few errors occuring in one of our screens but only in the PBD version.
When we run the PBL code via PowerBuilder (with or without debug brekapoints) it never fails.
One of the problems is that a computed field is showing up in the pfc_sort field selection dropdown even though there is explicit code to exclude it.
dw_master Constructor
String ls_exclude[]
ls_exclude[1] = "compute_1"
dw_master.inv_sort.of_SetExclude(ls_exclude)
dw_master.inv_filter.of_SetExclude(ls_exclude)
The other problem is an actual application crash when opening another window via OpenSheetWithParm().
I am looking for tips and/or pointers on how to approach this.
When we run the PBL code via PowerBuilder (with or without debug brekapoints) it never fails.
One of the problems is that a computed field is showing up in the pfc_sort field selection dropdown even though there is explicit code to exclude it.
dw_master Constructor
String ls_exclude[]
ls_exclude[1] = "compute_1"
dw_master.inv_sort.of_SetExclude(ls_exclude)
dw_master.inv_filter.of_SetExclude(ls_exclude)
The other problem is an actual application crash when opening another window via OpenSheetWithParm().
I am looking for tips and/or pointers on how to approach this.
Talk To Other Members
RE: Need tips on debugging possible memory-leak
Turns out the window object had been inadvertantly saved into another PBL.
When testing via PowerBuilder, my test PBL was above the other PBL so my code always executed.
After making a build, the PBD order was such that an older version of the object was found prior to the correct object and thus overrode it.
The fix was to delete the 2nd copy of the object from the incorrect PBL and rebuild the PBDs so there is only one definition of the object.
- Bill
RE: Need tips on debugging possible memory-leak
"Nature forges everything on the anvil of time"
www.anvil-of-time.com
RE: Need tips on debugging possible memory-leak