Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: No DebOut lines appearing in SysInternals Date: Wed, 9 Sep 2020 15:45:11 +0200 Lines: 37 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: individual.net KBoNYlI5CYEv25PaE0XpjgL+dkgaai5dciBU6YuUUFaQromYc= Cancel-Lock: sha1:kPik89dLlNwGVpCmOU4pj1GHxnw= User-Agent: XanaNews/1.18.1.6 Xref: csiph.com comp.lang.clipper.visual-objects:13071 Hi Ross, the correct function in VO 2.x should be DebOut() alone, and as a more powerful viewer you can use DebugView++ https://debugviewpp.wordpress.com/ But for profiling I would not use that, but instead write to a file using the FOpen(), FWrite() and FClose() functions. Wolfgang Ross wrote: > Hello, > > I am trying to get some detail on how long certain areas of code are > taking to run but am currently unable to see any information. > > Based on what I've searched for and found in this group, the > instructions for using DebOut32 seem straightforward. > > Add a line such as - _DebOut32(psz("starting calculation")) to the > code near the beginning of a method or function. > > Make your exe. > > Run your exe and then look in DebugView for the line you've added. > > However, it does not seem to be working. > > If anyone can offer any suggestion or detail that I might have missed > it would be much appreciated. --