Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #13070 > unrolled thread
| Started by | Ross <ross.howie@gmail.com> |
|---|---|
| First post | 2020-09-09 06:19 -0700 |
| Last post | 2020-09-10 08:50 -0700 |
| Articles | 4 — 3 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
No DebOut lines appearing in SysInternals Ross <ross.howie@gmail.com> - 2020-09-09 06:19 -0700
Re: No DebOut lines appearing in SysInternals "Wolfgang Riedmann" <wriedmann@gmail.com> - 2020-09-09 15:45 +0200
Re: No DebOut lines appearing in SysInternals Robert Pope <cooeee@gmail.com> - 2020-09-10 07:23 -0700
Re: No DebOut lines appearing in SysInternals Ross <ross.howie@gmail.com> - 2020-09-10 08:50 -0700
| From | Ross <ross.howie@gmail.com> |
|---|---|
| Date | 2020-09-09 06:19 -0700 |
| Subject | No DebOut lines appearing in SysInternals |
| Message-ID | <faa21762-9718-40f5-ba3e-4d01534b0bc3n@googlegroups.com> |
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.
[toc] | [next] | [standalone]
| From | "Wolfgang Riedmann" <wriedmann@gmail.com> |
|---|---|
| Date | 2020-09-09 15:45 +0200 |
| Message-ID | <hrs4j7FaaamU1@mid.individual.net> |
| In reply to | #13070 |
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.
--
[toc] | [prev] | [next] | [standalone]
| From | Robert Pope <cooeee@gmail.com> |
|---|---|
| Date | 2020-09-10 07:23 -0700 |
| Message-ID | <05b0c359-5ef1-42c9-9273-ff73bb859b2fo@googlegroups.com> |
| In reply to | #13071 |
On Wednesday, September 9, 2020 at 11:45:14 PM UTC+10, Wolfgang Riedmann wrote:
> 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.
>
>
>
> --
DebOut() appears to be a wrapper to _DebOut32().
If DebOut() doesn't work, you can use the OutputDebugString() Windows API call instead. That was how I got around _DebOut32() not working (I didn't try DebOut).
Doco: https://docs.microsoft.com/en-us/windows/win32/api/debugapi/nf-debugapi-outputdebugstringa
[toc] | [prev] | [next] | [standalone]
| From | Ross <ross.howie@gmail.com> |
|---|---|
| Date | 2020-09-10 08:50 -0700 |
| Message-ID | <66d1c349-cb82-4342-a68d-a57ee81963cen@googlegroups.com> |
| In reply to | #13074 |
Many thanks. OutputDebugString() has worked a treat!
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web