LogTrace - A DLL to log trace output to a file

Environment: MSVC 5.0

The code was designed to build a dll to log trace statements to a text file at customer sites. At the end of the day the customers emails me the text log.
To use the LogTrace.dll in your project add LogTrace.lib to the Object/Library modules in your linker settings and include the header Trace.h to your project.

In your InitInstance() call


	TraceStart();

or

	TraceReadINI();

After that you can call Trace() like printf or TRACE

	Trace("This is my string value [%s]\n", m_strMessage);  //Works like printf or TRACE

Exported functions

TraceStart(char *pszPathName = NULL) A call to TraceStart() will start tracing until end of execution or TraceStop(). The log will default to the directory of the application that called it. You can over ride the default behavior by passing in your own path, file name and file name extension. The existing log is always numerically archived. If more than one instance of an application is executing, then susequent applications will have the post fix 'HMODULE' in the log entries.
TraceReadINI() Reads control values from the applications ini file.

[TRACE]
;Specific log name and path
PathAndFileName=C:\A_TEST\mylog.txt
;1: file will be flushed after every Trace(), 0: no flushing
FLUSH=0

If you use TraceReadINI then you do not have to use TraceStart.
Trace(const char *pszFormat, ...) Works just like TRACE() or printf(). The first parameter can be any length, the sum of the additional parameters is limited to 1024 characters.
TraceSuspend(bool bTrueToSuspend) When true logging is suspended until set back to false.
Default is false
TraceStop() The current log is closed. To continue logging, explicitly call TraceStart(). In the event of multiple programs writing to the same log, the log will not be closed. The next call to TraceStart() will append to the existing log.
TraceClockCapture(char* pszComment = NULL) Captures the current clock value.
TraceClockDuration (char* pszComment = NULL) Writes the number of seconds passed since the last TraceClockCapture().
TraceFlush(bool bForceFlush) You can turn it off to increase performance, but if the application fails you may not get the last several dozen statements logged written to the log file.
Default is true.
TraceWithTime(bool bValue) Causes the Trace() statement to output the time of each trace statement. The year value is not output.
Default is true.

Download source - 10KB



Comments

  • Request for change.

    Posted by Legacy on 02/28/1999 12:00am

    Originally posted by: Brain Koch

    Can this be modified to write to a zipped file, rather than a text file?

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • On-demand Event Event Date: September 10, 2014 Modern mobile applications connect systems-of-engagement (mobile apps) with systems-of-record (traditional IT) to deliver new and innovative business value. But the lifecycle for development of mobile apps is also new and different. Emerging trends in mobile development call for faster delivery of incremental features, coupled with feedback from the users of the app "in the wild." This loop of continuous delivery and continuous feedback is how the best mobile …

  • Targeted attacks and advanced threats are customized to infiltrate your unique IT infrastructure, evade conventional defenses, and remain hidden while stealing your corporate data. To detect these criminal intrusions, analysts and security experts agree that organizations should deploy advanced threat protection as part of an expanded security monitoring strategy. For this comparative analysis of breach detection systems, product analysis reports and comparative analysis reports are used to create the security …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds