Interpreting oeprofile.log (OpenInsight 32-bit Specific)
At 16 JUN 2004 12:15:26AM Wilhelm Schmitt wrote:
How is the oeprofile.log to be interpreted with entries like:
CALCULATEX 313
or XMLDICT 235 47
or TTS_MFS 250 0 ?
Regards
Wilhelm
At 16 JUN 2004 02:25AM [email protected] wrote:
Generally these refer to the time the routine was entered and how long was spent in there. So you can profile how long was spent in each section of code. We do have some internal tools to play with these but for now they won't be on release in NOLA… (:-] Sorry Sig
)
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 16 JUN 2004 03:34AM Pat McNerthney wrote:
Upon entry into a subroutine, an entry of the form:
~CallDepthAsSpaces~ROUTINE_NAME ~ClockTicksSinceStart~is logged. Upon exit, and entry of the form:
~CallDepthAsSpaces~ROUTINE_NAME ~ClockTicksSinceStart~ ~ClockTicksInRoutine~is logged.
Need any further clarification? It should be very straight forward to write a Basic+ routine which crunches on this data.
Pat
At 16 JUN 2004 09:56AM [email protected] wrote:
that's it man!! NO reason to go to NO now
except for the Hurricanes ..
[email protected] onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"
David Tod Sigafoos ~ SigSolutions
At 17 JUN 2004 09:49AM Wilhelm Schmitt wrote:
Thanks Pat,
are there any plans to extend the options, I mean towards debugging remote engines?
Example: writing also the line number that forced a routine to break.
Regards
Wilhelm