Re: Trace debugging in run-time (re-direct Debug.Print to a file?)
- From: "Tony Proctor" <tony_proctor@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 2 Jul 2007 14:06:14 +0100
You could use a file logging class that is safe to use with multiple
processes and/or threads Sinna, e.g.
http://groups.google.co.uk/group/microsoft.public.vb.com/msg/e2e67b2bdfc0ae5b?hl=en&;
Tony Proctor
"Sinna" <news4sinna_NOSPAM@xxxxxxxxxx> wrote in message
news:eBTs$SHvHHA.3816@xxxxxxxxxxxxxxxxxxxxxxx
gh wrote:
Hi,Look in MSDN for OutputDebugString. It doesn't redirect to a file, but
I want to see all the steps at debugging without watching any specific
variables, breakpoint...!
Is it possible to re-direct?
I'm using vb6 and can not find any hint on how to do in MSDN.
Thanks
gh
to the Debug Console/View. Download DbgView from SysInternals (now MS)
and see you debugging info passing by.
Note that I'm not redirecting you to a file-based logging as it has some
overhead and possible issues as Windows doesn't update the log file
every time you write a line to it. So if your application crashes it's
possible you don't have the complete log.
If you want to save the debug info to a file, you can use the
save-function of DbgView.
Another reason I don't use file-based logging is to avoid collisions
when multiple instances of the application are open.
Sinna
.
- Follow-Ups:
- References:
- Prev by Date: Re: CDate problem
- Next by Date: Re: Code Editor Annoyance; mouse wheel
- Previous by thread: Re: Trace debugging in run-time (re-direct Debug.Print to a file?)
- Next by thread: Re: Trace debugging in run-time (re-direct Debug.Print to a file?)
- Index(es):
Relevant Pages
|
